Error trying to restart service
After the weekend I came in to run the checks on our logs and noticed nothing new had been written over the weekend, or at least since mid-night last night. When I tried to restart the service, I got an error saying that the "user; user=root" and "group; group=root" could not be verified. I am stuck in a meeting at the moment and was wondering if anyone could offer any advice on how to quickly resolve this, once I get back to my desk? Thanks, James McDonald System Administrator RHCSA, Security+ jmcdonald@lce.com
James McDonald <jmcdonald@LCE.com> writes:
After the weekend I came in to run the checks on our logs and noticed nothing new had been written over the weekend, or at least since mid-night last night. When I tried to restart the service, I got an error saying that the "user; user=root" and "group; group=root" could not be verified. I am stuck in a meeting at the moment and was wondering if anyone could offer any advice on how to quickly resolve this, once I get back to my desk?
Which version of syslog-ng? How exactly did you try to restart it? Is everything all right with the init script? Is the message coming from syslog-ng, or the init script, or something else? -- |8]
We are using version 4.0.1a. I am using 'service syslog-ng restart.' Below is the output I get from running that command: [root@server-name ~]# service syslog-ng restart WARNING: Configuration file format is too old, please update it to use the 4.1 format as some constructs might operate inefficiently; WARNING: global: the default value of log_fifo_size() has changed to 10000 in syslog-ng 4.1 to reflect log_iw_size() changes for tcp()/udp() window size changes; Error resolving user; user='root' Error resolving group; group='root' Restarting syslog-ng: Stopping syslog-ng: [ OK ] Starting syslog-ng: WARNING: Configuration file format is too old, please update it to use the 4.1 format as some constructs might operate inefficiently; WARNING: global: the default value of log_fifo_size() has changed to 10000 in syslog-ng 4.1 to reflect log_iw_size() changes for tcp()/udp() window size changes; [ OK ] -----Original Message----- From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of Gergely Nagy Sent: Monday, July 02, 2012 9:45 AM To: Syslog-ng users' and developers' mailing list Subject: Re: [syslog-ng] Error trying to restart service James McDonald <jmcdonald@LCE.com> writes:
After the weekend I came in to run the checks on our logs and noticed nothing new had been written over the weekend, or at least since mid-night last night. When I tried to restart the service, I got an error saying that the "user; user=root" and "group; group=root" could not be verified. I am stuck in a meeting at the moment and was wondering if anyone could offer any advice on how to quickly resolve this, once I get back to my desk?
Which version of syslog-ng? How exactly did you try to restart it? Is everything all right with the init script? Is the message coming from syslog-ng, or the init script, or something else? -- |8] ____________________________________________________________________________ __ Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng FAQ: http://www.balabit.com/wiki/syslog-ng-faq
James McDonald <jmcdonald@LCE.com> writes:
We are using version 4.0.1a. I am using 'service syslog-ng restart.' Below is the output I get from running that command:
Ah, if it is PE, then I'd suggest you contact us via BOSS. This list is for the OpenSource Edition of syslog-ng. Nevertheless:
[root@server-name ~]# service syslog-ng restart WARNING: Configuration file format is too old, please update it to use the 4.1 format as some constructs might operate inefficiently; WARNING: global: the default value of log_fifo_size() has changed to 10000 in syslog-ng 4.1 to reflect log_iw_size() changes for tcp()/udp() window size changes; Error resolving user; user='root' Error resolving group; group='root'
This suggests that syslog-ng can't figure out what uid the root user has. This usually means that /etc/passwd is borked, or Name Server Switch functionality (see /etc/nsswitch.conf) is somehow not working. -- |8]
I am trying to verify if we have a registered BOSS account. I checked both the passwd and nsswitch files and they looked fine. Other services that I restarted (as root) did not produce the error that I get when I try to restart the syslog-ng service. -----Original Message----- From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of Gergely Nagy Sent: Monday, July 02, 2012 10:54 AM To: Syslog-ng users' and developers' mailing list Subject: Re: [syslog-ng] Error trying to restart service James McDonald <jmcdonald@LCE.com> writes:
We are using version 4.0.1a. I am using 'service syslog-ng restart.' Below is the output I get from running that command:
Ah, if it is PE, then I'd suggest you contact us via BOSS. This list is for the OpenSource Edition of syslog-ng. Nevertheless:
[root@server-name ~]# service syslog-ng restart WARNING: Configuration file format is too old, please update it to use the 4.1 format as some constructs might operate inefficiently; WARNING: global: the default value of log_fifo_size() has changed to 10000 in syslog-ng 4.1 to reflect log_iw_size() changes for tcp()/udp() window size changes; Error resolving user; user='root' Error resolving group; group='root'
This suggests that syslog-ng can't figure out what uid the root user has. This usually means that /etc/passwd is borked, or Name Server Switch functionality (see /etc/nsswitch.conf) is somehow not working. -- |8] ____________________________________________________________________________ __ Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng FAQ: http://www.balabit.com/wiki/syslog-ng-faq
I have noticed that the error only appears when I try a 'restart'. Stop|start|status do not produce the error. I don't know if that has any bearing on what the problem may be or not, but I thought I would share it anyway. -----Original Message----- From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of Gergely Nagy Sent: Monday, July 02, 2012 10:54 AM To: Syslog-ng users' and developers' mailing list Subject: Re: [syslog-ng] Error trying to restart service James McDonald <jmcdonald@LCE.com> writes:
We are using version 4.0.1a. I am using 'service syslog-ng restart.' Below is the output I get from running that command:
Ah, if it is PE, then I'd suggest you contact us via BOSS. This list is for the OpenSource Edition of syslog-ng. Nevertheless:
[root@server-name ~]# service syslog-ng restart WARNING: Configuration file format is too old, please update it to use the 4.1 format as some constructs might operate inefficiently; WARNING: global: the default value of log_fifo_size() has changed to 10000 in syslog-ng 4.1 to reflect log_iw_size() changes for tcp()/udp() window size changes; Error resolving user; user='root' Error resolving group; group='root'
This suggests that syslog-ng can't figure out what uid the root user has. This usually means that /etc/passwd is borked, or Name Server Switch functionality (see /etc/nsswitch.conf) is somehow not working. -- |8] ____________________________________________________________________________ __ Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng FAQ: http://www.balabit.com/wiki/syslog-ng-faq
----- Original message -----
James McDonald <jmcdonald@LCE.com> writes:
We are using version 4.0.1a. I am using 'service syslog-ng restart.' Below is the output I get from running that command:
Ah, if it is PE, then I'd suggest you contact us via BOSS. This list is for the OpenSource Edition of syslog-ng.
Nevertheless:
[root@server-name ~]# service syslog-ng restart WARNING: Configuration file format is too old, please update it to use the 4.1 format as some constructs might operate inefficiently; WARNING: global: the default value of log_fifo_size() has changed to 10000 in syslog-ng 4.1 to reflect log_iw_size() changes for tcp()/udp() window size changes; Error resolving user; user='root' Error resolving group; group='root'
This suggests that syslog-ng can't figure out what uid the root user has. This usually means that /etc/passwd is borked, or Name Server Switch functionality (see /etc/nsswitch.conf) is somehow not working.
also, the logs indicate that it is v4.1 and not v4.0 and v4.1 should be upgraded as that is a feature release with short term support periods, v4.2 superseeded it (after 3 months past the release date) but anyway the support guys should be helpful to resolve this issue.
participants (3)
-
Balazs Scheidler
-
Gergely Nagy
-
James McDonald