Could the cause for the problem be the following constellation: host <-> docker : both use the same FB ? I suspect that after quitting the docker, it might set the tmp/firebird in the above state. What mechanism should FB use, to prevent the above situation ?
Am Do., 1. Juli 2021 um 14:48 Uhr schrieb Pro Turm <protu...@gmail.com>: > I have the same situation again. How can I find out, whats causes, i.e. > sets the tmp/firebird in this situation ? > > > > *$ sudo ls -laR /tmp/firebird/tmp/firebird:total 44* > > > > > *drwxrwx--- 2 84 84 4096 Jun 30 21:56 .drwxrwxrwt 33 root > root 36864 Jul 1 14:44 ..-rw-rw---- 1 firebird firebird 0 Jun > 30 11:24 fb_init-rw------- 1 root root 0 Jun 30 11:24 > fb_rename_guard* > > Am Mi., 30. Juni 2021 um 11:32 Uhr schrieb Pro Turm <protu...@gmail.com>: > >> most probably the *84 *(It was *UID* sorry, so it has probably nothing >> to do with *kauditd*) is a *bug* from a previous FB4.0Beta or similar >> installation. >> >> Even though I stop the firebird service, the process remained being >> executed: >> >> *84 603870 603770 0 09:52 ? 00:00:00 >> /opt/firebird/bin/fbguard -pidfile /var/run/firebird/firebird.pid -daemon >> -forever84 603871 603870 0 09:52 ? 00:00:00 >> /opt/firebird/bin/firebird* >> >> I had to kill them explicitly. After which, executing ./install.sh on a >> clean system produced the following: >> *ps -efaww --headers | grep firebird* >> >> *UID PID PPID C STIME TTY TIME CMD* >> >> *firebird 630407 1 0 11:24 ? 00:00:00 >> /opt/firebird/bin/fbguard -daemon -foreverfirebird 630411 630407 0 11:24 >> ? 00:00:00 /opt/firebird/bin/firebird* >> >> Am Mi., 30. Juni 2021 um 11:11 Uhr schrieb Pro Turm <protu...@gmail.com>: >> >>> The install script has the following command >>> *ps -efaww | egrep "\<(firebird\$|[[:space:]])" | grep -v grep | grep -v >>> -w '\-path'* >>> which returns >>> *84 603871 603870 0 09:52 ? 00:00:00 >>> /opt/firebird/bin/firebird* >>> >>> Even though I had removed the */opt/firebird* before I executed the >>> above command and had executed *sysctl service firebird stop* >>> >>> According to *ps* the *PID==84* is kauditd >>> >>> That is to say, I cannot understand how it comes to the *84* dealing >>> with *firebird* ? >>> >>> >>> Am Mi., 30. Juni 2021 um 10:53 Uhr schrieb Alex Peshkoff via >>> Firebird-devel <firebird-devel@lists.sourceforge.net>: >>> >>>> On 6/30/21 11:42 AM, Pro Turm wrote: >>>> > /$ sudo ls -laR /tmp/firebird >>>> > /tmp/firebird: >>>> > total 44 >>>> > drwxrwx--- 2 84 84 4096 Jun 29 20:38 . >>>> > drwxrwxrwt 31 root root 36864 Jun 30 10:42 .. >>>> > -rw-rw---- 1 firebird firebird 0 Jun 28 11:07 fb_init >>>> > -rw------- 1 root root 0 Jun 28 11:07 fb_rename_guard/ >>>> > >>>> > Am Mi., 30. Juni 2021 um 10:40 Uhr schrieb Alex Peshkoff via >>>> > Firebird-devel <firebird-devel@lists.sourceforge.net >>>> > <mailto:firebird-devel@lists.sourceforge.net>>: >>>> > >>>> > On 6/30/21 11:21 AM, Pro Turm wrote: >>>> > > Hi, >>>> > > Does anyone know the reason for the following? >>>> > > >>>> > > /Operating system call access failed. Error code 20/ >>>> > > / >>>> > > / >>>> > > /ConfigStorage: Cannot initialize the shared memory region >>>> > > operating system directive access failed >>>> > > Not a directory/ >>>> > > / >>>> > > / >>>> > > /Authentication error >>>> > > operating system directive access failed >>>> > > Not a directory/ >>>> > > >>>> > >>>> > send here output of >>>> > ls -laR /tmp/firebird >>>> > >>>> >>>> Remove the whole /tmp/firebird (root access needed) - it's owned by >>>> unknown user with ID=84, should be firebird. >>>> >>>> >>>> >>>> Firebird-Devel mailing list, web interface at >>>> https://lists.sourceforge.net/lists/listinfo/firebird-devel >>>> >>>
Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel