Dear All,,
Kindly help me out
As i am going to login to firewall at webpage the error is showing and i cannot go to web access,,
"Ooooops: Session: Configured save path '/var/lib/webconfig/session' is not writable by the PHP process"
what does it means,, kindly help me, i unable to login
Kindly help me out
As i am going to login to firewall at webpage the error is showing and i cannot go to web access,,
"Ooooops: Session: Configured save path '/var/lib/webconfig/session' is not writable by the PHP process"
what does it means,, kindly help me, i unable to login
Share this post:
Responses (6)
-
Accepted Answer
-
Accepted Answer
Nick Howitt wrote:
What is the output to:ls -l /var/lib/webconfig/
df -h
[root@gateway ~]# ls -l /var/lib/webconfig/
total 624
drwxrwx---. 2 root webconfig 634880 Nov 9 15:45 session
[root@gateway ~]# ls -l /var/lib/webconfig/
total 624
drwxrwx---. 2 root webconfig 634880 Nov 9 15:45 session
[root@gateway ~]# df -h
Filesystem Size Used Avail Use% Mounted on
devtmpfs 3.9G 0 3.9G 0% /dev
tmpfs 3.9G 0 3.9G 0% /dev/shm
tmpfs 3.9G 411M 3.5G 11% /run
tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup
/dev/mapper/clearos-root 817G 2.2G 774G 1% /
/dev/sda1 976M 199M 710M 22% /boot
/dev/mapper/clearos-var 83G 13G 66G 17% /var
tmpfs 797M 0 797M 0% /run/user/992
tmpfs 797M 0 797M 0% /run/user/0 -
Accepted Answer
-
Accepted Answer
I have no idea what is going on. You have heaps of space and the config directory is correctly owned. Can you try restarting the webconfig with a:
[/quote]systemctl restart webconfig
Dear Nick Howitt,,
is restarting will change or reset the firewall settings,, means will it goes to default setting.. -
Accepted Answer
Dear Nick Howitt..
its not restarting...
Last login: Sat Nov 9 15:07:00 2019 from pc-wasa.wasaprinter.com
[root@gateway ~]# systemctl restart webconfig
Job for webconfig.service failed because the control process exited with error c ode. See "systemctl status webconfig.service" and "journalctl -xe" for details.
[root@gateway ~]# systemctl status webconfig.service
● webconfig.service - The Webconfig Apache HTTP Server
Loaded: loaded (/usr/lib/systemd/system/webconfig.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Mon 2019-11-11 18:28:31 PKT; 26s ago
Docs: man:httpd(8)
man:apachectl(8)
Process: 26722 ExecStop=/usr/sbin/webconfig $OPTIONS -k graceful-stop (code=exited, status=0/SUCCESS)
Process: 26718 ExecStart=/usr/sbin/webconfig $OPTIONS -DFOREGROUND (code=exited, status=1/FAILURE)
Process: 26714 ExecStartPre=/usr/libexec/webconfig/prestart.sh (code=exited, status=0/SUCCESS)
Main PID: 26718 (code=exited, status=1/FAILURE)
Nov 11 18:28:31 gateway.wasaprinter.com prestart.sh[26714]: /usr/libexec/webconfig/prestart.sh: line 25: /var/tmp/servername.conf.clearos: Read-only file system
Nov 11 18:28:31 gateway.wasaprinter.com prestart.sh[26714]: mv: cannot stat ‘/var/tmp/servername.conf.clearos’: No such file or directory
Nov 11 18:28:31 gateway.wasaprinter.com webconfig[26718]: (30)Read-only file system: AH00091: webconfig: could not open error log file /usr/clearos/sandbox/etc/httpd/logs/error_log.
Nov 11 18:28:31 gateway.wasaprinter.com webconfig[26718]: AH00015: Unable to open logs
Nov 11 18:28:31 gateway.wasaprinter.com systemd[1]: webconfig.service: main process exited, code=exited, status=1/FAILURE
Nov 11 18:28:31 gateway.wasaprinter.com webconfig[26722]: httpd (no pid file) not running
Nov 11 18:28:31 gateway.wasaprinter.com systemd[1]: Failed to start The Webconfig Apache HTTP Server.
Nov 11 18:28:31 gateway.wasaprinter.com systemd[1]: Unit webconfig.service entered failed state.
Nov 11 18:28:31 gateway.wasaprinter.com systemd[1]: webconfig.service failed. -
Accepted Answer
Nov 11 18:28:31 gateway.wasaprinter.com prestart.sh[26714]: /usr/libexec/webconfig/prestart.sh: line 25: /var/tmp/servername.conf.clearos: Read-only file system
This worries me and I wonder if you have a damaged disk for file system. It may be worth grabbing a copy of your configuration back up from /var/clearos/configuration_backup in case you have to reload your system. Also back up whatever user data you require then consider rebooting.
before rebooting, force the system to check the root partition on reboot:touch /forcefsck
Alternatively you can check the file system manually. Google "check file system linux". Here are a couple of links #1 and #2. For me, the easiest way to determine the partitions you have is with the "blkid" command.
Please login to post a reply
You will need to be logged in to be able to post a reply. Login using the form on the right or register an account if you are new here.
Register Here »