Web interface not working after reboot

Support
,
1

NethServer Version: 7
Module: DC, File Server, Mail

Hi Team,

I need help on my new Nethserver setup, following are issues.

  1. I has been deploy one Nethserver 7 and update using web interface
  2. I has been configured DC and File server module and it’s working fine.
  3. After reboot server I am not able to open web management interface but I am able to ssh.

Kindly suggest we, I has been installed server two time but same issue

2

Which management interface, nethgui (port 980) or cockpit (port 9090)?
What do you see when trying to access the web management interface (blank page, error message…)?

4

What does the error message says?

Is httpd-admin service up & running?

systemctl -l status httpd-admin
5

9 posts were split to a new topic: Server-manager not accessible and network connection lost

10

httpd[5288]: (30)Read-only file system: AH00091: httpd: could not open error log file /var/log/httpd-admin/error_log.

11

Jan 24 23:18:23 dc1.mehp.com httpd[5288]: (30)Read-only file system: AH00091: httpd: could not open error log file /var/log/httpd-admin/error_log.
Jan 24 23:18:23 dc1.mehp.com httpd[5288]: AH00015: Unable to open logs

12

Try choosing a previous kernel when booting.
Check for warnings/errors on /var/log/messages and journalctl

13

Is this know issue on updated kernel

14

No. But some time ago we found a read-only filesystem caused by wrong fstab parameters and kernel update.

15

I have just add ACL for windows file share

16

journalctl shall provide you with clues for the cause of read-only file system. If the error happened after manually editing fstab then you can temporarily try by commenting those entries.

21

I am new for this community but in my post other discussion going on, i need solution on my post.

22

Access to server-manger is an effect of the read-only filesystem.
Did you try any of the above suggestions (booting with older kernel, commenting manually added fstab entries, searched journalctl)?

journalctl -b -x

or with the command suggested on-screen when boot fails.

23

There is no option for older kernel in booting and all file showing red only.

24

Some commands so you can provide us with more details:

uname -r
rpm -q kernel
cat /etc/fstab

Checking journal errors would be fine.
In case of filesystem corruption you could boot into rescue mode to repair it.