Re: [systemd-devel] Unit dovecot.service has failed

2019-10-07 Thread Masaru Kitajima
I’m sorry for my poor English and misunderstanding. I’ve created a new account and post a new ticket. Thanks again. > 2019/10/07 18:47、Reindl Harald のメール: > > jesus that was a sample bugreport, in that case for Fedora > > just write a new one for RHEL at https://bugzilla.redhat.com/

Re: [systemd-devel] Unit dovecot.service has failed

2019-10-07 Thread Reindl Harald
Am 07.10.19 um 10:16 schrieb Masaru Kitajima: > Hi, Mr. Harald. > > I went to see the page you told me, > https://bugzilla.redhat.com/show_bug.cgi?id=1748322 but I couldn't find > almost nothinh. > > But one thing I'm sure is I don't have service named "gssproxy." > > I have no idea... Do

Re: [systemd-devel] Unit dovecot.service has failed

2019-10-07 Thread Masaru Kitajima
v153-127-250-223.vir.kagoya.net crond[130]: (app) ERROR (getpwnam() failed) 10月 07 16:50:08 v153-127-250-223.vir.kagoya.net systemd[1]: dovecot.service start operation timed out. Terminating. 10月 07 16:50:08 v153-127-250-223.vir.kagoya.net dovecot[29554]: log: Warning: Killed with signal 15 (

Re: [systemd-devel] Unit dovecot.service has failed

2019-10-03 Thread Masaru Kitajima
Hi, Me. Harald Thank you very much for the explnations. I will go and see the link about /run after my quiet time thid morning. About bugreport, what I wanted to ask was the path in my server. Regards, Masaru > 2019/10/03 17:30、Reindl Harald のメール: > > Am 03.10.19 um 05:23 schrieb Masaru

Re: [systemd-devel] Unit dovecot.service has failed

2019-10-03 Thread Reindl Harald
Am 03.10.19 um 05:23 schrieb Masaru Kitajima: > I couldn’t catch the meaning about "that should be /run to begin with.” /var/run is for many years a symlink to /run as you can also see in the stat call newer versions of systemd starting to warn - it's about time to get that cleaned up after 8

Re: [systemd-devel] Unit dovecot.service has failed

2019-10-02 Thread Masaru Kitajima
Thank you. I got it. <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> iOS Engineer / WEB Engineer / UI/UX Designer / VFX director Masaru Kitajima E-mail: thirstytrave...@mac.com MMS: skul...@ezweb.ne.jp Facebook: https://www.facebook.com/masaru.kitajima (Request required) Twitter:

Re: [systemd-devel] Unit dovecot.service has failed

2019-10-02 Thread Mantas Mikulėnas
On Thu, Oct 3, 2019, 06:24 Masaru Kitajima wrote: > Mr. Harald > > Thank you so much for the detailed information. I tried two commands which > you kindly suggested. The results are as below. > > [root@vhost /var/log]# stat /var/run > File: `/var/run' -> `../run' > Size: 6

Re: [systemd-devel] Unit dovecot.service has failed

2019-10-02 Thread Masaru Kitajima
Mr. Harald Thank you so much for the detailed information. I tried two commands which you kindly suggested. The results are as below. [root@vhost /var/log]# stat /var/run File: `/var/run' -> `../run' Size: 6 Blocks: 0 IO Block: 4096 symbolic link Device:

Re: [systemd-devel] Unit dovecot.service has failed

2019-10-02 Thread Reindl Harald
Am 02.10.19 um 22:45 schrieb Masaru Kitajima: Oct. 02 16:49:14 v153-127-250-223.vir.kagoya.net systemd[1]: Can't open PID file /var/run/dovecot/master.pid (yet?) after start: Too many levels of symbolic links in old systemd versions that happend when something used in namespaces

[systemd-devel] Unit dovecot.service has failed

2019-10-02 Thread Masaru Kitajima
ith signal 15 (by pid=1 uid=0 code=kill) Oct. 02 16:50:44 MyIPAddress.vir.kagoya.net systemd[1]: Failed to start Dovecot IMAP/POP3 email server. -- Subject: Unit dovecot.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel