Re: FW: Resource temporarily unavailable while reading from system.journal

Hi Laszlo,

I am running a debian10 with syslog-ng 3.32.
If using the default syslog-ng configuration for Debian 10, the error is
reproducible.
It happened to me when stimulating the syslog-ng using logger command.

Sorry for the delay in reply.

Thanks and regards,
Alex

On Wed, Aug 18, 2021 at 9:39 AM Alexandre Santos <[email protected]>
wrote:

>
>
>
>
> *From:* syslog-ng <[email protected]> * On Behalf Of *Laszlo
> Szemere (lszemere)
> *Sent:* 17 de agosto de 2021 15:20
> *To:* Syslog-ng users' and developers' mailing list <
> [email protected]>
> *Subject:* Re: [syslog-ng] Resource temporarily unavailable while reading
> from system.journal
>
>
>
> Hello Alex,
>
>
>
> sorry for not responding sooner.
>
>
>
> From my experience, the most common reasons behind this error messages are:
>
>
>
> 1) Syslog-ng do not have the proper permissions to read /dev/log
>
> 2) /dev/log is already opened by an another process. (Maybe Syslog-ng
> started multiple times.)
>
>
>
>
>
> If the problem still exists, please share the details of your platform and
> I will try to reproduce your problem with the attached configuration.
>
>
>
>
>
> Best regards,
>
> Laszlo
>
>
> ------------------------------
>
> *From:* syslog-ng <[email protected]> on behalf of
> Alexandre Santos <[email protected]>
> *Sent:* Thursday, August 12, 2021 15:40
> *To:* Syslog-ng users' and developers' mailing list <
> [email protected]>
> *Subject:* [syslog-ng] Resource temporarily unavailable while reading
> from system.journal
>
>
>
> Hi,
>
>
>
> I am seeing the following strace log when running the syslog-ng 3.32 with
> the configuration in the attachment:
>
> root@myhost:/home/shared# sudo strace -f -yyy -s 256 -e trace=read -p 2539
> strace: Process 2539 attached with 4 threads
> [pid  2539] read(48<anon_inode:[timerfd]>, "\1\0\0\0\0\0\0\0", 8) = 8
> [pid  2539] read(11<anon_inode:inotify>,
> "\2\0\0\0\2\0\0\0\0\0\0\0\20\0\0\0system.journal\0\0", 272) = 32
> [pid  2539] read(11<anon_inode:inotify>, 0x7ffda019f930, 272) = -1 EAGAIN
> (Resource temporarily unavailable)
> [pid  2539] read(11<anon_inode:inotify>,
> "\2\0\0\0\2\0\0\0\0\0\0\0\20\0\0\0system.journal\0\0", 272) = 32
> [pid  2539] read(11<anon_inode:inotify>, 0x7ffda019f930, 272) = -1 EAGAIN
> (Resource temporarily unavailable)
> [pid  2539] read(11<anon_inode:inotify>,
> "\2\0\0\0\2\0\0\0\0\0\0\0\20\0\0\0system.journal\0\0", 272) = 32
> [pid  2539] read(11<anon_inode:inotify>, 0x7ffda019f930, 272) = -1 EAGAIN
> (Resource temporarily unavailable)
> [pid  2539] read(11<anon_inode:inotify>,
> "\2\0\0\0\2\0\0\0\0\0\0\0\20\0\0\0system.journal\0\0", 272) = 32
> [pid  2539] read(11<anon_inode:inotify>, 0x7ffda019f930, 272) = -1 EAGAIN
> (Resource temporarily unavailable)
> [pid  2539] read(11<anon_inode:inotify>,
> "\2\0\0\0\2\0\0\0\0\0\0\0\20\0\0\0system.journal\0\0", 272) = 32
> [pid  2539] read(11<anon_inode:inotify>, 0x7ffda019f930, 272) = -1 EAGAIN
> (Resource temporarily unavailable)
> [pid  2539] read(11<anon_inode:inotify>,
> "\2\0\0\0\2\0\0\0\0\0\0\0\20\0\0\0system.journal\0\0", 272) = 32
> [pid  2539] read(11<anon_inode:inotify>, 0x7ffda019f930, 272) = -1 EAGAIN
> (Resource temporarily unavailable)
> [pid  2539] read(11<anon_inode:inotify>,
> "\2\0\0\0\2\0\0\0\0\0\0\0\20\0\0\0system.journal\0\0", 272) = 32
> [pid  2539] read(11<anon_inode:inotify>, 0x7ffda019f930, 272) = -1 EAGAIN
> (Resource temporarily unavailable)
> [pid  2539] read(11<anon_inode:inotify>,
> "\2\0\0\0\2\0\0\0\0\0\0\0\20\0\0\0system.journal\0\0", 272) = 32
> [pid  2539] read(11<anon_inode:inotify>, 0x7ffda019f930, 272) = -1 EAGAIN
> (Resource temporarily unavailable)
> [pid  2539] read(11<anon_inode:inotify>,
> "\2\0\0\0\2\0\0\0\0\0\0\0\20\0\0\0system.journal\0\0", 272) = 32
> [pid  2539] read(11<anon_inode:inotify>, 0x7ffda019f930, 272) = -1 EAGAIN
> (Resource temporarily unavailable)
> ^Cstrace: Process 2539 detached
> strace: Process 11623 detached
> strace: Process 20518 detached
> strace: Process 22517 detached
>
>
>
> This normal behaviour?
>
>
>
> Thanks & Regards,
>
> Alex
>

______________________________________________________________________________
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