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

can not log into Webadmin, REST API disabled

Hi,

When is start the browser and try to log into https://ip_of_utm:4444/ the UTM responds with: REST API Disabled. Enable in WebAdmin Settings > REST API.

How can i circumvent this? The WebAdmin is not acessible for me anymore.

Is there a possibility to do this from CLI?

 



This thread was automatically locked due to age.
  • Hi Fred,

    Restart HTTPD service. Execute the following command in shell as root.

    /etc/init.d/httpd restart

    Thanks

    Sachin Gurung
    Team Lead | Sophos Technical Support
    Knowledge Base  |  @SophosSupport  |  Video tutorials
    Remember to like a post.  If a post (on a question thread) solves your question use the 'This helped me' link.

  • Hi sachingurung,

    that helped.

    best regards,

    Fred

  • I've noticed that this has been happening quite a bit since I upgraded to 9.411-3 on a virtual machine. Are others seeing the same thing? The web interface becomes unresponsive, then starts giving the Rest API error and in some cases the UTM needs to be rebooted to recover.

  • I'm not seeing this elsewhere, Josh, but none of my clients use a VM to host UTM.  I would suspect a broken installation.  If restoring the backup made prior to the last application of Up2Dates doesn't stop this phenomenon, you might want to try reinstalling from ISO and restoring from a backup.

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • on a fresh install no. On an upgraded install seen it before.

  • Thank you for the answer, also today i have experienced this behaviour. With latest Up2Date.

     

  • I've only started noticing this on my UTMs since they were upgraded to 9.411-3. I've tried fresh installs of the same version, and the same thing happens. I've noticed this in the http daemon logs at the time of the issue. The only fix that works for me is to reboot the UTM.

    2017:03:20-11:12:22 tbutmlis httpd[6587]: [fcgid:error] [pid 6587] (30)Read-only file system: mod_fcgid: couldn't bind unix domain socket /tmp/sock/6587.109
    2017:03:20-11:12:23 tbutmlis httpd[6587]: [fcgid:error] [pid 6587] (30)Read-only file system: mod_fcgid: couldn't bind unix domain socket /tmp/sock/6587.110
    2017:03:20-11:12:24 tbutmlis httpd[6587]: [fcgid:error] [pid 6587] (30)Read-only file system: mod_fcgid: couldn't bind unix domain socket /tmp/sock/6587.111
    2017:03:20-11:12:25 tbutmlis httpd[6587]: [fcgid:error] [pid 6587] (30)Read-only file system: mod_fcgid: couldn't bind unix domain socket /tmp/sock/6587.112
    2017:03:20-11:12:26 tbutmlis httpd[6587]: [fcgid:error] [pid 6587] (30)Read-only file system: mod_fcgid: couldn't bind unix domain socket /tmp/sock/6587.113
    2017:03:20-11:12:27 tbutmlis httpd[6587]: [fcgid:error] [pid 6587] (30)Read-only file system: mod_fcgid: couldn't bind unix domain socket /tmp/sock/6587.114
    2017:03:20-11:12:28 tbutmlis httpd[6587]: [fcgid:error] [pid 6587] (30)Read-only file system: mod_fcgid: couldn't bind unix domain socket /tmp/sock/6587.115
    2017:03:20-11:12:29 tbutmlis httpd[6584]: [core:error] [pid 6584] (30)Read-only file system: AH00095: failed to remove PID file /var/run/httpd.pid
    2017:03:20-11:12:30 tbutmlis httpd[7559]: [socache_dbm:error] [pid 7559] (30)Read-only file system: AH00804: Cannot create socache DBM file `/tmp/http.ssl_scache'
    2017:03:20-11:12:30 tbutmlis httpd[7559]: [ssl:emerg] [pid 7559] AH01874: Could not initialize session cache. Exiting.
    2017:03:20-11:12:44 tbutmlis httpd[7775]: [socache_dbm:error] [pid 7775] (30)Read-only file system: AH00804: Cannot create socache DBM file `/tmp/http.ssl_scache'
    2017:03:20-11:12:44 tbutmlis httpd[7775]: [ssl:emerg] [pid 7775] AH01874: Could not initialize session cache. Exiting.

  • System dump seems to indicate an issue writing to the file system at the time the issue occurs. Seems to lose connection to the DB.

     

    2017:03:20-13:42:17 <firewallname> ntpd[5921]: receive: KoD packet from <ipaddress> has inconsistent xmt/org/rec timestamps. Ignoring.
    2017:03:20-13:42:26 <firewallname> postgres[3942]: [2-1] LOG: could not open temporary statistics file "pg_stat_tmp/pgstat.tmp": Read-only file system<134>Mar 20 13:42:26 postgres[3942]: [3-1] LOG: could not open temporary statistics file "pg_stat_tmp/pgstat.tmp": Read-only file system
    2017:03:20-13:42:26 <firewallname> postgres[3942]: [4-1] LOG: could not open temporary statistics file "pg_stat_tmp/pgstat.tmp": Read-only file system
    2017:03:20-13:42:26 <firewallname> postgres[3942]: [5-1] LOG: could not open temporary statistics file "pg_stat_tmp/pgstat.tmp": Read-only file system
    2017:03:20-13:42:26 <firewallname> postgres[3942]: [6-1] LOG: could not open temporary statistics file "pg_stat_tmp/pgstat.tmp": Read-only file system
    2017:03:20-13:42:26 <firewallname> postgres[3942]: [7-1] LOG: could not open temporary statistics file "pg_stat_tmp/pgstat.tmp": Read-only file system
    2017:03:20-13:42:26 <firewallname> postgres[3942]: [8-1] LOG: could not open temporary statistics file "pg_stat_tmp/pgstat.tmp": Read-only file system
    2017:03:20-13:42:26 <firewallname> postgres[3942]: [9-1] LOG: could not open temporary statistics file "pg_stat_tmp/pgstat.tmp": Read-only file system
    2017:03:20-13:42:26 <firewallname> postgres[3942]: [10-1] LOG: could not open temporary statistics file "pg_stat_tmp/pgstat.tmp": Read-only file system
    2017:03:20-13:42:21 <firewallname> postgres[3939]: [2-1] PANIC: could not fdatasync log file 0, segment 4: Input/output error
    2017:03:20-13:42:26 <firewallname> postgres[3935]: [3-1] LOG: WAL writer process (PID 3939) was terminated by signal 6: Aborted<134>Mar 20 13:42:26 postgres[3935]: [4-1] LOG: terminating any other active server processes
    2017:03:20-13:42:26 <firewallname> postgres[6008]: [3-1] WARNING: terminating connection because of crash of another server process<133>Mar 20 13:42:26 postgres[6008]: [3-2] DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
    2017:03:20-13:42:26 <firewallname> postgres[6008]: [3-3] HINT: In a moment you should be able to reconnect to the database and repeat your command.
    2017:03:20-13:42:26 <firewallname> postgres[5019]: [3-1] WARNING: terminating connection because of crash of another server process<133>Mar 20 13:42:26 postgres[5019]: [3-2] DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
    2017:03:20-13:42:26 <firewallname> postgres[5019]: [3-3] HINT: In a moment you should be able to reconnect to the database and repeat your command.
    2017:03:20-13:42:26 <firewallname> postgres[4929]: [3-1] WARNING: terminating connection because of crash of another server process<133>Mar 20 13:42:26 postgres[4929]: [3-2] DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
    2017:03:20-13:42:26 <firewallname> postgres[4929]: [3-3] HINT: In a moment you should be able to reconnect to the database and repeat your command.
    2017:03:20-13:42:26 <firewallname> postgres[4729]: [3-1] WARNING: terminating connection because of crash of another server process<133>Mar 20 13:42:26 postgres[4729]: [3-2] DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
    2017:03:20-13:42:26 <firewallname> postgres[4729]: [3-3] HINT: In a moment you should be able to reconnect to the database and repeat your command.
    2017:03:20-13:42:26 <firewallname> postgres[4717]: [3-1] WARNING: terminating connection because of crash of another server process<133>Mar 20 13:42:26 postgres[4717]: [3-2] DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
    2017:03:20-13:42:26 <firewallname> postgres[4717]: [3-3] HINT: In a moment you should be able to reconnect to the database and repeat your command.
    2017:03:20-13:42:26 <firewallname> postgres[4678]: [3-1] WARNING: terminating connection because of crash of another server process<133>Mar 20 13:42:26 postgres[4678]: [3-2] DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
    2017:03:20-13:42:26 <firewallname> postgres[4678]: [3-3] HINT: In a moment you should be able to reconnect to the database and repeat your command.
    2017:03:20-13:42:26 <firewallname> postgres[4677]: [3-1] WARNING: terminating connection because of crash of another server process<133>Mar 20 13:42:26 postgres[4677]: [3-2] DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
    2017:03:20-13:42:26 <firewallname> postgres[4677]: [3-3] HINT: In a moment you should be able to reconnect to the database and repeat your command.
    2017:03:20-13:42:26 <firewallname> postgres[4627]: [3-1] WARNING: terminating connection because of crash of another server process<133>Mar 20 13:42:26 postgres[4627]: [3-2] DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
    2017:03:20-13:42:26 <firewallname> postgres[4627]: [3-3] HINT: In a moment you should be able to reconnect to the database and repeat your command.
    2017:03:20-13:42:26 <firewallname> postgres[3940]: [3-1] WARNING: terminating connection because of crash of another server process<133>Mar 20 13:42:26 postgres[3940]: [3-2] DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
    2017:03:20-13:42:26 <firewallname> postgres[3940]: [3-3] HINT: In a moment you should be able to reconnect to the database and repeat your command.
    2017:03:20-13:42:26 <firewallname> postgres[3942]: [11-1] LOG: could not open temporary statistics file "global/pgstat.tmp": Read-only file system
    2017:03:20-13:42:26 <firewallname> postgres[3935]: [5-1] LOG: archiver process (PID 3941) exited with exit code 1
    2017:03:20-13:42:26 <firewallname> postgres[3935]: [6-1] LOG: all server processes terminated; reinitializing
    2017:03:20-13:42:26 <firewallname> postgres[3935]: [7-1] LOG: could not open file "postmaster.pid": Read-only file system
    2017:03:20-13:42:26 <firewallname> postgres[3935]: [8-1] PANIC: could not open control file "global/pg_control": Read-only file system
    2017:03:20-13:42:26 <firewallname> ulogd[4624]: pg1: server closed the connection unexpectedly
    2017:03:20-13:42:27 <firewallname> ulogd[4624]: pg1: connect: could not connect to server: Connection refused
    2017:03:20-13:42:32 <firewallname> ulogd[4624]: pg1: connect: could not connect to server: Connection refused
    2017:03:20-13:42:34 <firewallname> ntpd[5921]: receive: KoD packet from <ipaddress> has inconsistent xmt/org/rec timestamps. Ignoring.
    2017:03:20-13:42:37 <firewallname> ulogd[4624]: pg1: connect: could not connect to server: Connection refused
    2017:03:20-13:42:41 <firewallname> syslog-ng[4660]: Configuration reload request received, reloading configuration;
    2017:03:20-13:42:42 <firewallname> ulogd[4624]: pg1: connect: could not connect to server: Connection refused
    2017:03:20-13:42:47 <firewallname> ulogd[4624]: pg1: connect: could not connect to server: Connection refused
    2017:03:20-13:42:52 <firewallname> ulogd[4624]: pg1: connect: could not connect to server: Connection refused
    2017:03:20-13:42:52 <firewallname> ntpd[5921]: receive: KoD packet from <ipaddress> has inconsistent xmt/org/rec timestamps. Ignoring.
    2017:03:20-13:42:57 <firewallname> ulogd[4624]: pg1: connect: could not connect to server: Connection refused

  • Interestingly, enabling the REST API seems to have stopped that issue occurring.. 1 hour and counting.

  • I have this problem, and enabling REST API did not resolve the issue.  After about 20 minutes uptime the webadmin stops responding.

     

    Since enabling REST API, I can't log in to the console either.  I get a message about all configuration is done with WebAdmin, and it won't allow logins at the console.