View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0004572SOGosogo-toolpublic2018-10-15 07:072018-10-16 14:25
Reporterdanbet Assigned To 
PrioritynormalSeveritytweakReproducibilityalways
Status newResolutionopen 
PlatformLinuxOSDebian GNU/LinuxOS Version9
Product Version4.0.2 
Summary0004572: Error with socket /dev/log after upgrade from debian jessie to stretch
Description

The nightly cron job of the sogo-backup give me this two lines of errors after I upgraded my debian system from jessie to stretch:

logger: Socket /dev/log: Keine Berechtigung
logger: Socket /dev/log: Keine Berechtigung

The backup is not done, no files are created, only the directory that should contain them.

The job runs at 00:30 under the user sogo
30 0 * sogo /usr/sbin/sogo-backup

The file /dev/log is a link
lrwxrwxrwx 1 root root 28 Okt 14 03:06 /dev/log -> /run/systemd/journal/dev-log

The linked file has the following permissions
srw-rw---- 1 root sudo 0 Okt 14 03:06 /run/systemd/journal/dev-log

Under jessie they was
lrwxrwxrwx 1 root root 28 Okt 13 23:06 /dev/log -> /run/systemd/journal/dev-log=
srw-rw---- 1 root sudo 0 Okt 13 23:06 /run/systemd/journal/dev-log=

There were no such problem under Debian Jessie, the job runs successfully under the user sogo. Has it to run under root in stretch?

TagsNo tags attached.

Activities

Christian Mack

Christian Mack

2018-10-16 07:17

developer   ~0013107

Did you enable SELinux or AppArmor on upgrading?
danbet

danbet

2018-10-16 09:33

reporter   ~0013110

No, I don't.

The permissions does not allow the user sogo read or write access to the file /run/systemd/journal/dev-log. This was already so at jessie. What I don't understand is the = character after the file name in jessie.

I have added the user sogo to the group sudo, now the backup runs.

I don't know the sogo-backup has to be run under the user sogo or root.
danbet

danbet

2018-10-16 14:25

reporter   ~0013113

Ah, I see. The script sogo-backup (is eventially from debian) calls sogo-tool backup and pipes the result to logger. The problem seems to be the logger, not sogo-tool. Anyway, if logger generates an error, no backups are done.

Issue History

Date Modified Username Field Change
2018-10-15 07:07 danbet New Issue
2018-10-16 07:17 Christian Mack Note Added: 0013107
2018-10-16 09:33 danbet Note Added: 0013110
2018-10-16 14:25 danbet Note Added: 0013113