From mboxrd@z Thu Jan 1 00:00:00 1970 From: ummeegge To: development@lists.ipfire.org Subject: Re: Core update 132 - Tor does not start after update Date: Sun, 26 May 2019 17:05:20 +0200 Message-ID: <216c66064533e3c1f890320ede010b47a1f6f0b3.camel@ipfire.org> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============5501694033027124435==" List-Id: --===============5501694033027124435== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi all, opened up a ticket --> https://bugzilla.ipfire.org/show_bug.cgi?id=3D12088 . Best, Erik On Fr, 2019-05-24 at 07:37 +0200, ummeegge wrote: > Hi all, > could track the problem done to this patch --> >=20 https://git.ipfire.org/?p=3Dipfire-2.x.git;a=3Dcommit;h=3D2df98063a246dc1f17b= ae7fd0e477d7f73e2319f > if i change the user back to nobody i can start the tor service again > via tor.cgi . >=20 > It seems that according to the switch to new user/group 'tor' some > permissions does not match > properly. >=20 > Best, >=20 > Erik >=20 > On Do, 2019-05-23 at 19:47 +0200, ummeegge wrote: > > Possibly only a fate of an individual... > >=20 > > Erik > >=20 > > On Do, 2019-05-23 at 14:56 +0200, ummeegge wrote: > > > Starting tor via commandline by simply typing > > >=20 > > > tor > > >=20 > > > 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. > > >=20 > > > Currently not sure how to debug it further... > > >=20 > > > On Do, 2019-05-23 at 14:41 +0200, ummeegge wrote: > > > > On Do, 2019-05-23 at 13:31 +0100, Michael Tremer wrote: > > > > > Hi, > > > > >=20 > > > > > > On 23 May 2019, at 13:30, ummeegge > > > > > > wrote: > > > > > >=20 > > > > > > 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: > > > > >=20 > > > > > Which problem persists? > > > >=20 > > > > Tor do not want to start > > > > >=20 > > > > > If you have installed the library it cannot be missing any > > > > > more. > > > >=20 > > > > 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. > > > >=20 > > > > >=20 > > > > > > [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. > > > > >=20 > > > > > These are all warnings. You can send a patch if you like. The > > > > > messages tell you what to change :) > > > >=20 > > > > 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 ;-) . > > > >=20 > > > > >=20 > > > > > -Michael > > > > >=20 > > > > > >=20 > > > > > >=20 > > > > > >=20 > > > > > > On Do, 2019-05-23 at 13:13 +0100, Michael Tremer wrote: > > > > > > > Did you try installing libseccomp? > > > > > > >=20 > > > > > > > > On 23 May 2019, at 13:12, ummeegge > > > > > > > > > > > > > > > > wrote: > > > > > > > >=20 > > > > > > > > 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 > > > > > > > >=20 > > > > > > > > /usr/bin/tor: error while loading shared libraries: > > > > > > > > libseccomp.so.2: cannot open shared object file: No > > > > > > > > such > > > > > > > > file > > > > > > > > or > > > > > > > > directory > > > > > > > >=20 > > > > > > > > Best, > > > > > > > >=20 > > > > > > > > Erik > > > > > > > >=20 > > > > > > >=20 > > > > > > >=20 > > > > >=20 > > > > >=20 > > > >=20 > > > >=20 > > >=20 > > >=20 >=20 >=20 --===============5501694033027124435==--