Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 6 subscribers
  • Views 5205 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Sophos Webadmin stops working after successful login while showing "Please wait, logging in" banner

ArnoZ

Hi community.

Sophos SG 125 HA Cluster [Master/Slave]
After Updating to the latest Firmware we cannot login to Webadmin because after successful Login it stops working while showing "Please wait, logging in" banner.

I tried several things without success:
- Cluster Restart, also httpd Restart
- Delete Browser Cache
- Tried different Browser
- Tried older Browser
- Tried different Locations
- Tried different Users
- Checked feed.xml (no such file)
- checked marketing_options (with value=0 and 1)
- Even SUM Webadmin Login fails in the same way
- Disk Space Usage all ok
- CPU Usage all ok
- UserPortal working perfectly with admin Account

Infos About Cluster:
- Status -----------------------------------------------------------------------
Current mode: HA SLAVE with id 2 in state ACTIVE
-- Nodes -----------------------------------------------------------------------
SLAVE: 2 AZ-WF2 198.19.250.2 9.510005 ACTIVE since Fri Oct 26 16:53:25 2018
MASTER: 1 AZ-WF1 198.19.250.1 9.510005 ACTIVE since Fri Oct 26 16:48:25 2018
-- Load ------------------------------------------------------------------------
Node  2: [1m] 0.35  [5m] 0.20  [15m] 0.39
Node  1: [1m] 0.06  [5m] 0.17  [15m] 0.47

- Kernel -----------------------------------------------------------------------
Current mode: enabled slave
interface: eth3
Local ID: 198.19.250.2
Master ID: 1
debug: off
verbose: off
ppp sync: off
port smtp: 25
port pop3: 8110
port ftp: 2121

- PostgreSQL ------------------------------------------------------------------------
 primary | standby |     lag      |  bytelag
---------+---------+--------------+----------
       1 |       2 | 00:00:03.531 |        0

httpd log:
2018:10:26-17:54:58 az-wf-01-1 httpd[21764]: [core:error] [pid 21764] [client **.*.***.**:26839] Premature end of script headers: webadmin.plx, referer: https://**.***.**.***:4444/
2018:10:26-17:54:58 az-wf-01-1 httpd[21764]: [core:error] [pid 21764] [client **.*.***.**:26839] End of script output before headers: webadmin.plx, referer: https://**.***.**.***:4444/
2018:10:26-17:54:58 az-wf-01-1 httpd: **.*.***.** - - [26/Oct/2018:17:54:54 +0200] "POST /webadmin.plx HTTP/1.1" 500 -

I can fully connect via SSH.
Perhaps someone has resolved something like this or has a idea for me.

Thanks in Advance
ArnoZ



This thread was automatically locked due to age.
Parents
  • 0

    Hi ArnoZ,

    if you can login to via SSH and run

    /etc/rc.d/httpd restart 

    does it work after that again or is that just happening constantly with every single login?

     EDIT: (just read again and saw you already tried that) If that doesnt work maybe middleware restart helps? /etc/init.d/mdw restart

    Regards

    Jason

    Regards

    Jason

    Sophos Certified Architect - UTM

  • 0 in reply to Jason Klein

    Hallo Jason.

    As written i tried this with no succes.

    <M> az-wf-01:/root # /etc/rc.d/httpd restart
    :: Stopping WebAdmin                                                 done
    :: Starting WebAdmin                                                 done
    :: Restarting WebAdmin

    And it is that just happening constantly with every single login.

  • 0 in reply to ArnoZ

    Hi Arnoz,

     

    dann machen wir auf deutsch weiter.

    Ich habe folgende zwei Möglichkeiten mal gelesen:

    1.


    löschen /var/sec/chroot-httpd/var/webadmin/var/feed.xml
      
      
    dann /etc/init.d/httpd restart

    -habe ich noch nie ausprobiert habe aber mal vor einiger Zeit gelesen, dass das geholfen haben soll

     

    2.

     

    Ein altes Backup in das Root directory von einem Stick speicher evtl. eines von vor dem Update und dann den anstecken, sollte ja dann automatisch davon booten.

    Ich glaube viel mehr Möglichkeiten hat man da nicht. Mal schauen wer da noch etwas dazu weiß.
      

    Regards

    Jason

    Sophos Certified Architect - UTM

  • 0 in reply to Jason Klein

    Hey Jason.

    0. Restarted Middleware too: /etc/init.d/mdw restart
    But without success.

    1. Cannot find any feed.xml in the system:
    <M> az-wf-01:/root # find / -name feed.xml 2> /dev/null
    <M> az-wf-01:/root #

    2. Boot with older Backup
    <M> az-wf-01:/root # backup.plx -l
    [...]
    cfg_4496_1539738000     SUM-Auto-Backup system  Wed Oct 17 03:00:00 2018
    cfg_22690_1539812649    Automatic Backup (Up2Date 9.510005)     system  Wed Oct 17 23:44:09 2018
    [...]
    <M> az-wf-01:/root # backup.plx -n cfg_4496_1539738000 -i
    Backup restored.
    <M> az-wf-01:/root #

    Restoring to the last Backup before (Up2Date 9.510005) worked for me.

    Thxs for this hint. ArnoZ

  • 0 in reply to ArnoZ

    Hallo Arno and welcome to the UTM Community!

    "Restoring to the last Backup before (Up2Date 9.510005) worked for me."

    Exactly what I was going to suggest.  Thanks for posting the answer in English so that more people can understand.  And for showing the command line alternative to Jason's suggestion.  There is a trick to doing the restore in High Availability by booting with a backup in the root directory of a FAT32 USB memory stick - the Slave must be taken down before rebooting the Master node.

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Reply
  • 0 in reply to ArnoZ

    Hallo Arno and welcome to the UTM Community!

    "Restoring to the last Backup before (Up2Date 9.510005) worked for me."

    Exactly what I was going to suggest.  Thanks for posting the answer in English so that more people can understand.  And for showing the command line alternative to Jason's suggestion.  There is a trick to doing the restore in High Availability by booting with a backup in the root directory of a FAT32 USB memory stick - the Slave must be taken down before rebooting the Master node.

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Children
No Data
Unfiltered HTML