On Mon, Jun 28, 2021 at 10:16 AM Joe Wong <[email protected]> wrote:
> > > On Mon, Jun 28, 2021 at 10:10 AM Benny Pedersen <[email protected]> wrote: > >> On 2021-06-28 03:19, Joe Wong wrote: >> >> > What did I miss here ? >> >> >> https://askubuntu.com/questions/197459/how-to-fix-sudo-unable-to-open-read-only-file-system >> >> for ubuntu here, i just think its same problem on centos >> > > Thanks Benny but there is no file systems error can be found at all in my > Centos7 box. > I delete /usr/var/run/dovecot, I can mkdir myself without error.. [root@new-ns1 run]# tail /var/log//messages Jun 28 09:53:41 new-ns1 systemd: Started dnf makecache. Jun 28 09:54:10 new-ns1 systemd: Started Dovecot IMAP/POP3 email server. Jun 28 09:54:10 new-ns1 dovecot: Fatal: mkdir(/usr/var/run/dovecot) failed: Read-only file system Jun 28 09:54:10 new-ns1 systemd: dovecot.service: main process exited, code=exited, status=89/n/a Jun 28 09:54:10 new-ns1 systemd: Unit dovecot.service entered failed state. Jun 28 09:54:10 new-ns1 systemd: dovecot.service failed. [root@new-ns1 run]# mkdir dovecot [root@new-ns1 run]# ls -l total 4 drwxr-xr-x 2 root root 4096 Jun 28 09:54 dovecot Moreover, if I launch dovecot manually /usr/sbin/dovecot -c /usr/local/etc/dovecot/dovecot.conf It does not complain of any error and I can login my mailbox via IMAP without any problem at all. I am running out of idea what could be the problem here. Something to do with user's privileges when running under systemd?
