Core update 132 - Tor does not start after update

Core update 132 - Tor does not start after update

[ummeegge]

[-- Attachment #1: Type: text/plain, Size: 282 bytes --]

Hi all,
wanted to report that after the update to Core 132 testing and a system
reboot that Tor does not starts anymore. Error is

/usr/bin/tor: error while loading shared libraries: libseccomp.so.2: cannot open shared object file: No such file or directory

Best,

Erik

Re: Core update 132 - Tor does not start after update

[Michael Tremer]

[-- Attachment #1: Type: text/plain, Size: 415 bytes --]

Did you try installing libseccomp?

> On 23 May 2019, at 13:12, ummeegge <ummeegge(a)ipfire.org> wrote:
> 
> Hi all,
> wanted to report that after the update to Core 132 testing and a system
> reboot that Tor does not starts anymore. Error is
> 
> /usr/bin/tor: error while loading shared libraries: libseccomp.so.2: cannot open shared object file: No such file or directory
> 
> Best,
> 
> Erik
> 

Re: Core update 132 - Tor does not start after update

[ummeegge]

[-- Attachment #1: Type: text/plain, Size: 1821 bytes --]

Hi Michael,
yes have seen that it is available in Pakfire after i compiled the
actual version 2.4.1 :D. But the problem persists. The error disappears
from torctrl restart but Apaches error_log points the following out:

[Thu May 23 14:26:19 2019] tor.cgi: Scalar value @pid[0] better written as $pid[0] at /srv/web/ipfire/cgi-bin/tor.cgi line 235.
[Thu May 23 14:26:19 2019] tor.cgi: Scalar value @pid[0] better written as $pid[0] at /srv/web/ipfire/cgi-bin/tor.cgi line 244.
[Thu May 23 14:26:19 2019] tor.cgi: "my" variable @cmds masks earlier declaration in same scope at /srv/web/ipfire/cgi-bin/tor.cgi line 949.
[Thu May 23 14:26:19 2019] tor.cgi: Name "Header::colourgreen" used only once: possible typo at /srv/web/ipfire/cgi-bin/tor.cgi line 239.
[Thu May 23 14:26:19 2019] tor.cgi: Name "Header::colourorange" used only once: possible typo at /srv/web/ipfire/cgi-bin/tor.cgi line 565.
[Thu May 23 14:26:19 2019] tor.cgi: Name "Header::colouryellow" used only once: possible typo at /srv/web/ipfire/cgi-bin/tor.cgi line 35.
[Thu May 23 14:26:20 2019] tor.cgi: Use of uninitialized value in addition (+) at /srv/web/ipfire/cgi-bin/tor.cgi line 82.
[Thu May 23 14:26:20 2019] tor.cgi: Use of uninitialized value in addition (+) at /srv/web/ipfire/cgi-bin/tor.cgi line 82.



On Do, 2019-05-23 at 13:13 +0100, Michael Tremer wrote:
> Did you try installing libseccomp?
> 
> > On 23 May 2019, at 13:12, ummeegge <ummeegge(a)ipfire.org> wrote:
> > 
> > Hi all,
> > wanted to report that after the update to Core 132 testing and a
> > system
> > reboot that Tor does not starts anymore. Error is
> > 
> > /usr/bin/tor: error while loading shared libraries:
> > libseccomp.so.2: cannot open shared object file: No such file or
> > directory
> > 
> > Best,
> > 
> > Erik
> > 
> 
> 

Re: Core update 132 - Tor does not start after update

[Michael Tremer]

[-- Attachment #1: Type: text/plain, Size: 2151 bytes --]

Hi,

> On 23 May 2019, at 13:30, ummeegge <ummeegge(a)ipfire.org> wrote:
> 
> Hi Michael,
> yes have seen that it is available in Pakfire after i compiled the
> actual version 2.4.1 :D. But the problem persists. The error disappears
> from torctrl restart but Apaches error_log points the following out:

Which problem persists?

If you have installed the library it cannot be missing any more.

> [Thu May 23 14:26:19 2019] tor.cgi: Scalar value @pid[0] better written as $pid[0] at /srv/web/ipfire/cgi-bin/tor.cgi line 235.
> [Thu May 23 14:26:19 2019] tor.cgi: Scalar value @pid[0] better written as $pid[0] at /srv/web/ipfire/cgi-bin/tor.cgi line 244.
> [Thu May 23 14:26:19 2019] tor.cgi: "my" variable @cmds masks earlier declaration in same scope at /srv/web/ipfire/cgi-bin/tor.cgi line 949.
> [Thu May 23 14:26:19 2019] tor.cgi: Name "Header::colourgreen" used only once: possible typo at /srv/web/ipfire/cgi-bin/tor.cgi line 239.
> [Thu May 23 14:26:19 2019] tor.cgi: Name "Header::colourorange" used only once: possible typo at /srv/web/ipfire/cgi-bin/tor.cgi line 565.
> [Thu May 23 14:26:19 2019] tor.cgi: Name "Header::colouryellow" used only once: possible typo at /srv/web/ipfire/cgi-bin/tor.cgi line 35.
> [Thu May 23 14:26:20 2019] tor.cgi: Use of uninitialized value in addition (+) at /srv/web/ipfire/cgi-bin/tor.cgi line 82.
> [Thu May 23 14:26:20 2019] tor.cgi: Use of uninitialized value in addition (+) at /srv/web/ipfire/cgi-bin/tor.cgi line 82.

These are all warnings. You can send a patch if you like. The messages tell you what to change :)

-Michael

> 
> 
> 
> On Do, 2019-05-23 at 13:13 +0100, Michael Tremer wrote:
>> Did you try installing libseccomp?
>> 
>>> On 23 May 2019, at 13:12, ummeegge <ummeegge(a)ipfire.org> wrote:
>>> 
>>> Hi all,
>>> wanted to report that after the update to Core 132 testing and a
>>> system
>>> reboot that Tor does not starts anymore. Error is
>>> 
>>> /usr/bin/tor: error while loading shared libraries:
>>> libseccomp.so.2: cannot open shared object file: No such file or
>>> directory
>>> 
>>> Best,
>>> 
>>> Erik
>>> 
>> 
>> 
> 

Re: Core update 132 - Tor does not start after update

[ummeegge]

[-- Attachment #1: Type: text/plain, Size: 2792 bytes --]

On Do, 2019-05-23 at 13:31 +0100, Michael Tremer wrote:
> Hi,
> 
> > On 23 May 2019, at 13:30, ummeegge <ummeegge(a)ipfire.org> wrote:
> > 
> > Hi Michael,
> > yes have seen that it is available in Pakfire after i compiled the
> > actual version 2.4.1 :D. But the problem persists. The error
> > disappears
> > from torctrl restart but Apaches error_log points the following
> > out:
> 
> Which problem persists?

Tor do not want to start
> 
> If you have installed the library it cannot be missing any more.
Yes the error does not appear after executing 'torctrl restart' but
should this lib not be shiped with this update then ? Or even be part
of the core system ? Since the user do not knows why Tor stops working.

> 
> > [Thu May 23 14:26:19 2019] tor.cgi: Scalar value @pid[0] better
> > written as $pid[0] at /srv/web/ipfire/cgi-bin/tor.cgi line 235.
> > [Thu May 23 14:26:19 2019] tor.cgi: Scalar value @pid[0] better
> > written as $pid[0] at /srv/web/ipfire/cgi-bin/tor.cgi line 244.
> > [Thu May 23 14:26:19 2019] tor.cgi: "my" variable @cmds masks
> > earlier declaration in same scope at /srv/web/ipfire/cgi-
> > bin/tor.cgi line 949.
> > [Thu May 23 14:26:19 2019] tor.cgi: Name "Header::colourgreen" used
> > only once: possible typo at /srv/web/ipfire/cgi-bin/tor.cgi line
> > 239.
> > [Thu May 23 14:26:19 2019] tor.cgi: Name "Header::colourorange"
> > used only once: possible typo at /srv/web/ipfire/cgi-bin/tor.cgi
> > line 565.
> > [Thu May 23 14:26:19 2019] tor.cgi: Name "Header::colouryellow"
> > used only once: possible typo at /srv/web/ipfire/cgi-bin/tor.cgi
> > line 35.
> > [Thu May 23 14:26:20 2019] tor.cgi: Use of uninitialized value in
> > addition (+) at /srv/web/ipfire/cgi-bin/tor.cgi line 82.
> > [Thu May 23 14:26:20 2019] tor.cgi: Use of uninitialized value in
> > addition (+) at /srv/web/ipfire/cgi-bin/tor.cgi line 82.
> 
> These are all warnings. You can send a patch if you like. The
> messages tell you what to change :)
Humm... Am hanging currently on ovpnmain.cgi for a DH-Free PKI
generation (spare 400 lines of code and 1 minute generation time
{sounds good}?!?!? :) but ok will see what i can make ;-) .

> 
> -Michael
> 
> > 
> > 
> > 
> > On Do, 2019-05-23 at 13:13 +0100, Michael Tremer wrote:
> > > Did you try installing libseccomp?
> > > 
> > > > On 23 May 2019, at 13:12, ummeegge <ummeegge(a)ipfire.org> wrote:
> > > > 
> > > > Hi all,
> > > > wanted to report that after the update to Core 132 testing and
> > > > a
> > > > system
> > > > reboot that Tor does not starts anymore. Error is
> > > > 
> > > > /usr/bin/tor: error while loading shared libraries:
> > > > libseccomp.so.2: cannot open shared object file: No such file
> > > > or
> > > > directory
> > > > 
> > > > Best,
> > > > 
> > > > Erik
> > > > 
> > > 
> > > 
> 
> 

Re: Core update 132 - Tor does not start after update

[ummeegge]

[-- Attachment #1: Type: text/plain, Size: 3302 bytes --]

Starting tor via commandline by simply typing

tor

starts tor without problems and shows also the status in the tor.cgi
but if i stop it via Tor WUI and start it again also via WUI the status
stays at stop.

Currently not sure how to debug it further...

On Do, 2019-05-23 at 14:41 +0200, ummeegge wrote:
> On Do, 2019-05-23 at 13:31 +0100, Michael Tremer wrote:
> > Hi,
> > 
> > > On 23 May 2019, at 13:30, ummeegge <ummeegge(a)ipfire.org> wrote:
> > > 
> > > Hi Michael,
> > > yes have seen that it is available in Pakfire after i compiled
> > > the
> > > actual version 2.4.1 :D. But the problem persists. The error
> > > disappears
> > > from torctrl restart but Apaches error_log points the following
> > > out:
> > 
> > Which problem persists?
> 
> Tor do not want to start
> > 
> > If you have installed the library it cannot be missing any more.
> 
> Yes the error does not appear after executing 'torctrl restart' but
> should this lib not be shiped with this update then ? Or even be part
> of the core system ? Since the user do not knows why Tor stops
> working.
> 
> > 
> > > [Thu May 23 14:26:19 2019] tor.cgi: Scalar value @pid[0] better
> > > written as $pid[0] at /srv/web/ipfire/cgi-bin/tor.cgi line 235.
> > > [Thu May 23 14:26:19 2019] tor.cgi: Scalar value @pid[0] better
> > > written as $pid[0] at /srv/web/ipfire/cgi-bin/tor.cgi line 244.
> > > [Thu May 23 14:26:19 2019] tor.cgi: "my" variable @cmds masks
> > > earlier declaration in same scope at /srv/web/ipfire/cgi-
> > > bin/tor.cgi line 949.
> > > [Thu May 23 14:26:19 2019] tor.cgi: Name "Header::colourgreen"
> > > used
> > > only once: possible typo at /srv/web/ipfire/cgi-bin/tor.cgi line
> > > 239.
> > > [Thu May 23 14:26:19 2019] tor.cgi: Name "Header::colourorange"
> > > used only once: possible typo at /srv/web/ipfire/cgi-bin/tor.cgi
> > > line 565.
> > > [Thu May 23 14:26:19 2019] tor.cgi: Name "Header::colouryellow"
> > > used only once: possible typo at /srv/web/ipfire/cgi-bin/tor.cgi
> > > line 35.
> > > [Thu May 23 14:26:20 2019] tor.cgi: Use of uninitialized value in
> > > addition (+) at /srv/web/ipfire/cgi-bin/tor.cgi line 82.
> > > [Thu May 23 14:26:20 2019] tor.cgi: Use of uninitialized value in
> > > addition (+) at /srv/web/ipfire/cgi-bin/tor.cgi line 82.
> > 
> > These are all warnings. You can send a patch if you like. The
> > messages tell you what to change :)
> 
> Humm... Am hanging currently on ovpnmain.cgi for a DH-Free PKI
> generation (spare 400 lines of code and 1 minute generation time
> {sounds good}?!?!? :) but ok will see what i can make ;-) .
> 
> > 
> > -Michael
> > 
> > > 
> > > 
> > > 
> > > On Do, 2019-05-23 at 13:13 +0100, Michael Tremer wrote:
> > > > Did you try installing libseccomp?
> > > > 
> > > > > On 23 May 2019, at 13:12, ummeegge <ummeegge(a)ipfire.org>
> > > > > wrote:
> > > > > 
> > > > > Hi all,
> > > > > wanted to report that after the update to Core 132 testing
> > > > > and
> > > > > a
> > > > > system
> > > > > reboot that Tor does not starts anymore. Error is
> > > > > 
> > > > > /usr/bin/tor: error while loading shared libraries:
> > > > > libseccomp.so.2: cannot open shared object file: No such file
> > > > > or
> > > > > directory
> > > > > 
> > > > > Best,
> > > > > 
> > > > > Erik
> > > > > 
> > > > 
> > > > 
> > 
> > 
> 
> 

Re: Core update 132 - Tor does not start after update

[ummeegge]

[-- Attachment #1: Type: text/plain, Size: 3664 bytes --]

Possibly only a fate of an individual...

Erik

On Do, 2019-05-23 at 14:56 +0200, ummeegge wrote:
> Starting tor via commandline by simply typing
> 
> tor
> 
> starts tor without problems and shows also the status in the tor.cgi
> but if i stop it via Tor WUI and start it again also via WUI the
> status
> stays at stop.
> 
> Currently not sure how to debug it further...
> 
> On Do, 2019-05-23 at 14:41 +0200, ummeegge wrote:
> > On Do, 2019-05-23 at 13:31 +0100, Michael Tremer wrote:
> > > Hi,
> > > 
> > > > On 23 May 2019, at 13:30, ummeegge <ummeegge(a)ipfire.org> wrote:
> > > > 
> > > > Hi Michael,
> > > > yes have seen that it is available in Pakfire after i compiled
> > > > the
> > > > actual version 2.4.1 :D. But the problem persists. The error
> > > > disappears
> > > > from torctrl restart but Apaches error_log points the following
> > > > out:
> > > 
> > > Which problem persists?
> > 
> > Tor do not want to start
> > > 
> > > If you have installed the library it cannot be missing any more.
> > 
> > Yes the error does not appear after executing 'torctrl restart' but
> > should this lib not be shiped with this update then ? Or even be
> > part
> > of the core system ? Since the user do not knows why Tor stops
> > working.
> > 
> > > 
> > > > [Thu May 23 14:26:19 2019] tor.cgi: Scalar value @pid[0] better
> > > > written as $pid[0] at /srv/web/ipfire/cgi-bin/tor.cgi line 235.
> > > > [Thu May 23 14:26:19 2019] tor.cgi: Scalar value @pid[0] better
> > > > written as $pid[0] at /srv/web/ipfire/cgi-bin/tor.cgi line 244.
> > > > [Thu May 23 14:26:19 2019] tor.cgi: "my" variable @cmds masks
> > > > earlier declaration in same scope at /srv/web/ipfire/cgi-
> > > > bin/tor.cgi line 949.
> > > > [Thu May 23 14:26:19 2019] tor.cgi: Name "Header::colourgreen"
> > > > used
> > > > only once: possible typo at /srv/web/ipfire/cgi-bin/tor.cgi
> > > > line
> > > > 239.
> > > > [Thu May 23 14:26:19 2019] tor.cgi: Name "Header::colourorange"
> > > > used only once: possible typo at /srv/web/ipfire/cgi-
> > > > bin/tor.cgi
> > > > line 565.
> > > > [Thu May 23 14:26:19 2019] tor.cgi: Name "Header::colouryellow"
> > > > used only once: possible typo at /srv/web/ipfire/cgi-
> > > > bin/tor.cgi
> > > > line 35.
> > > > [Thu May 23 14:26:20 2019] tor.cgi: Use of uninitialized value
> > > > in
> > > > addition (+) at /srv/web/ipfire/cgi-bin/tor.cgi line 82.
> > > > [Thu May 23 14:26:20 2019] tor.cgi: Use of uninitialized value
> > > > in
> > > > addition (+) at /srv/web/ipfire/cgi-bin/tor.cgi line 82.
> > > 
> > > These are all warnings. You can send a patch if you like. The
> > > messages tell you what to change :)
> > 
> > Humm... Am hanging currently on ovpnmain.cgi for a DH-Free PKI
> > generation (spare 400 lines of code and 1 minute generation time
> > {sounds good}?!?!? :) but ok will see what i can make ;-) .
> > 
> > > 
> > > -Michael
> > > 
> > > > 
> > > > 
> > > > 
> > > > On Do, 2019-05-23 at 13:13 +0100, Michael Tremer wrote:
> > > > > Did you try installing libseccomp?
> > > > > 
> > > > > > On 23 May 2019, at 13:12, ummeegge <ummeegge(a)ipfire.org>
> > > > > > wrote:
> > > > > > 
> > > > > > Hi all,
> > > > > > wanted to report that after the update to Core 132 testing
> > > > > > and
> > > > > > a
> > > > > > system
> > > > > > reboot that Tor does not starts anymore. Error is
> > > > > > 
> > > > > > /usr/bin/tor: error while loading shared libraries:
> > > > > > libseccomp.so.2: cannot open shared object file: No such
> > > > > > file
> > > > > > or
> > > > > > directory
> > > > > > 
> > > > > > Best,
> > > > > > 
> > > > > > Erik
> > > > > > 
> > > > > 
> > > > > 
> > > 
> > > 
> > 
> > 
> 
> 

Re: Core update 132 - Tor does not start after update

[ummeegge]

[-- Attachment #1: Type: text/plain, Size: 4589 bytes --]

Hi all,
could track the problem done to this patch -->
https://git.ipfire.org/?p=ipfire-2.x.git;a=commit;h=2df98063a246dc1f17bae7fd0e477d7f73e2319f
if i change the user back to nobody i can start the tor service again via tor.cgi .

It seems that according to the switch to new user/group 'tor' some permissions does not match
properly.

Best,

Erik

On Do, 2019-05-23 at 19:47 +0200, ummeegge wrote:
> Possibly only a fate of an individual...
> 
> Erik
> 
> On Do, 2019-05-23 at 14:56 +0200, ummeegge wrote:
> > Starting tor via commandline by simply typing
> > 
> > tor
> > 
> > starts tor without problems and shows also the status in the
> > tor.cgi
> > but if i stop it via Tor WUI and start it again also via WUI the
> > status
> > stays at stop.
> > 
> > Currently not sure how to debug it further...
> > 
> > On Do, 2019-05-23 at 14:41 +0200, ummeegge wrote:
> > > On Do, 2019-05-23 at 13:31 +0100, Michael Tremer wrote:
> > > > Hi,
> > > > 
> > > > > On 23 May 2019, at 13:30, ummeegge <ummeegge(a)ipfire.org>
> > > > > wrote:
> > > > > 
> > > > > Hi Michael,
> > > > > yes have seen that it is available in Pakfire after i
> > > > > compiled
> > > > > the
> > > > > actual version 2.4.1 :D. But the problem persists. The error
> > > > > disappears
> > > > > from torctrl restart but Apaches error_log points the
> > > > > following
> > > > > out:
> > > > 
> > > > Which problem persists?
> > > 
> > > Tor do not want to start
> > > > 
> > > > If you have installed the library it cannot be missing any
> > > > more.
> > > 
> > > Yes the error does not appear after executing 'torctrl restart'
> > > but
> > > should this lib not be shiped with this update then ? Or even be
> > > part
> > > of the core system ? Since the user do not knows why Tor stops
> > > working.
> > > 
> > > > 
> > > > > [Thu May 23 14:26:19 2019] tor.cgi: Scalar value @pid[0]
> > > > > better
> > > > > written as $pid[0] at /srv/web/ipfire/cgi-bin/tor.cgi line
> > > > > 235.
> > > > > [Thu May 23 14:26:19 2019] tor.cgi: Scalar value @pid[0]
> > > > > better
> > > > > written as $pid[0] at /srv/web/ipfire/cgi-bin/tor.cgi line
> > > > > 244.
> > > > > [Thu May 23 14:26:19 2019] tor.cgi: "my" variable @cmds masks
> > > > > earlier declaration in same scope at /srv/web/ipfire/cgi-
> > > > > bin/tor.cgi line 949.
> > > > > [Thu May 23 14:26:19 2019] tor.cgi: Name
> > > > > "Header::colourgreen"
> > > > > used
> > > > > only once: possible typo at /srv/web/ipfire/cgi-bin/tor.cgi
> > > > > line
> > > > > 239.
> > > > > [Thu May 23 14:26:19 2019] tor.cgi: Name
> > > > > "Header::colourorange"
> > > > > used only once: possible typo at /srv/web/ipfire/cgi-
> > > > > bin/tor.cgi
> > > > > line 565.
> > > > > [Thu May 23 14:26:19 2019] tor.cgi: Name
> > > > > "Header::colouryellow"
> > > > > used only once: possible typo at /srv/web/ipfire/cgi-
> > > > > bin/tor.cgi
> > > > > line 35.
> > > > > [Thu May 23 14:26:20 2019] tor.cgi: Use of uninitialized
> > > > > value
> > > > > in
> > > > > addition (+) at /srv/web/ipfire/cgi-bin/tor.cgi line 82.
> > > > > [Thu May 23 14:26:20 2019] tor.cgi: Use of uninitialized
> > > > > value
> > > > > in
> > > > > addition (+) at /srv/web/ipfire/cgi-bin/tor.cgi line 82.
> > > > 
> > > > These are all warnings. You can send a patch if you like. The
> > > > messages tell you what to change :)
> > > 
> > > Humm... Am hanging currently on ovpnmain.cgi for a DH-Free PKI
> > > generation (spare 400 lines of code and 1 minute generation time
> > > {sounds good}?!?!? :) but ok will see what i can make ;-) .
> > > 
> > > > 
> > > > -Michael
> > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > On Do, 2019-05-23 at 13:13 +0100, Michael Tremer wrote:
> > > > > > Did you try installing libseccomp?
> > > > > > 
> > > > > > > On 23 May 2019, at 13:12, ummeegge <ummeegge(a)ipfire.org>
> > > > > > > wrote:
> > > > > > > 
> > > > > > > Hi all,
> > > > > > > wanted to report that after the update to Core 132
> > > > > > > testing
> > > > > > > and
> > > > > > > a
> > > > > > > system
> > > > > > > reboot that Tor does not starts anymore. Error is
> > > > > > > 
> > > > > > > /usr/bin/tor: error while loading shared libraries:
> > > > > > > libseccomp.so.2: cannot open shared object file: No such
> > > > > > > file
> > > > > > > or
> > > > > > > directory
> > > > > > > 
> > > > > > > Best,
> > > > > > > 
> > > > > > > Erik
> > > > > > > 
> > > > > > 
> > > > > > 
> > > > 
> > > > 
> > > 
> > > 
> > 
> > 

Re: Core update 132 - Tor does not start after update

[ummeegge]

[-- Attachment #1: Type: text/plain, Size: 5125 bytes --]

Hi all,
opened up a ticket --> https://bugzilla.ipfire.org/show_bug.cgi?id=12088 .

Best,

Erik

On Fr, 2019-05-24 at 07:37 +0200, ummeegge wrote:
> Hi all,
> could track the problem done to this patch -->
> 
https://git.ipfire.org/?p=ipfire-2.x.git;a=commit;h=2df98063a246dc1f17bae7fd0e477d7f73e2319f
> if i change the user back to nobody i can start the tor service again
> via tor.cgi .
> 
> It seems that according to the switch to new user/group 'tor' some
> permissions does not match
> properly.
> 
> Best,
> 
> Erik
> 
> On Do, 2019-05-23 at 19:47 +0200, ummeegge wrote:
> > Possibly only a fate of an individual...
> > 
> > Erik
> > 
> > On Do, 2019-05-23 at 14:56 +0200, ummeegge wrote:
> > > Starting tor via commandline by simply typing
> > > 
> > > tor
> > > 
> > > starts tor without problems and shows also the status in the
> > > tor.cgi
> > > but if i stop it via Tor WUI and start it again also via WUI the
> > > status
> > > stays at stop.
> > > 
> > > Currently not sure how to debug it further...
> > > 
> > > On Do, 2019-05-23 at 14:41 +0200, ummeegge wrote:
> > > > On Do, 2019-05-23 at 13:31 +0100, Michael Tremer wrote:
> > > > > Hi,
> > > > > 
> > > > > > On 23 May 2019, at 13:30, ummeegge <ummeegge(a)ipfire.org>
> > > > > > wrote:
> > > > > > 
> > > > > > Hi Michael,
> > > > > > yes have seen that it is available in Pakfire after i
> > > > > > compiled
> > > > > > the
> > > > > > actual version 2.4.1 :D. But the problem persists. The
> > > > > > error
> > > > > > disappears
> > > > > > from torctrl restart but Apaches error_log points the
> > > > > > following
> > > > > > out:
> > > > > 
> > > > > Which problem persists?
> > > > 
> > > > Tor do not want to start
> > > > > 
> > > > > If you have installed the library it cannot be missing any
> > > > > more.
> > > > 
> > > > Yes the error does not appear after executing 'torctrl restart'
> > > > but
> > > > should this lib not be shiped with this update then ? Or even
> > > > be
> > > > part
> > > > of the core system ? Since the user do not knows why Tor stops
> > > > working.
> > > > 
> > > > > 
> > > > > > [Thu May 23 14:26:19 2019] tor.cgi: Scalar value @pid[0]
> > > > > > better
> > > > > > written as $pid[0] at /srv/web/ipfire/cgi-bin/tor.cgi line
> > > > > > 235.
> > > > > > [Thu May 23 14:26:19 2019] tor.cgi: Scalar value @pid[0]
> > > > > > better
> > > > > > written as $pid[0] at /srv/web/ipfire/cgi-bin/tor.cgi line
> > > > > > 244.
> > > > > > [Thu May 23 14:26:19 2019] tor.cgi: "my" variable @cmds
> > > > > > masks
> > > > > > earlier declaration in same scope at /srv/web/ipfire/cgi-
> > > > > > bin/tor.cgi line 949.
> > > > > > [Thu May 23 14:26:19 2019] tor.cgi: Name
> > > > > > "Header::colourgreen"
> > > > > > used
> > > > > > only once: possible typo at /srv/web/ipfire/cgi-bin/tor.cgi
> > > > > > line
> > > > > > 239.
> > > > > > [Thu May 23 14:26:19 2019] tor.cgi: Name
> > > > > > "Header::colourorange"
> > > > > > used only once: possible typo at /srv/web/ipfire/cgi-
> > > > > > bin/tor.cgi
> > > > > > line 565.
> > > > > > [Thu May 23 14:26:19 2019] tor.cgi: Name
> > > > > > "Header::colouryellow"
> > > > > > used only once: possible typo at /srv/web/ipfire/cgi-
> > > > > > bin/tor.cgi
> > > > > > line 35.
> > > > > > [Thu May 23 14:26:20 2019] tor.cgi: Use of uninitialized
> > > > > > value
> > > > > > in
> > > > > > addition (+) at /srv/web/ipfire/cgi-bin/tor.cgi line 82.
> > > > > > [Thu May 23 14:26:20 2019] tor.cgi: Use of uninitialized
> > > > > > value
> > > > > > in
> > > > > > addition (+) at /srv/web/ipfire/cgi-bin/tor.cgi line 82.
> > > > > 
> > > > > These are all warnings. You can send a patch if you like. The
> > > > > messages tell you what to change :)
> > > > 
> > > > Humm... Am hanging currently on ovpnmain.cgi for a DH-Free PKI
> > > > generation (spare 400 lines of code and 1 minute generation
> > > > time
> > > > {sounds good}?!?!? :) but ok will see what i can make ;-) .
> > > > 
> > > > > 
> > > > > -Michael
> > > > > 
> > > > > > 
> > > > > > 
> > > > > > 
> > > > > > On Do, 2019-05-23 at 13:13 +0100, Michael Tremer wrote:
> > > > > > > Did you try installing libseccomp?
> > > > > > > 
> > > > > > > > On 23 May 2019, at 13:12, ummeegge <ummeegge(a)ipfire.org
> > > > > > > > >
> > > > > > > > wrote:
> > > > > > > > 
> > > > > > > > Hi all,
> > > > > > > > wanted to report that after the update to Core 132
> > > > > > > > testing
> > > > > > > > and
> > > > > > > > a
> > > > > > > > system
> > > > > > > > reboot that Tor does not starts anymore. Error is
> > > > > > > > 
> > > > > > > > /usr/bin/tor: error while loading shared libraries:
> > > > > > > > libseccomp.so.2: cannot open shared object file: No
> > > > > > > > such
> > > > > > > > file
> > > > > > > > or
> > > > > > > > directory
> > > > > > > > 
> > > > > > > > Best,
> > > > > > > > 
> > > > > > > > Erik
> > > > > > > > 
> > > > > > > 
> > > > > > > 
> > > > > 
> > > > > 
> > > > 
> > > > 
> > > 
> > > 
> 
>