From: ummeegge <ummeegge@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Core update 132 - Tor does not start after update
Date: Thu, 23 May 2019 14:30:03 +0200 [thread overview]
Message-ID: <f087df6467ac467f2a65b7c2857b1d45d8e9d219.camel@ipfire.org> (raw)
In-Reply-To: <C22EBA1A-01F2-4804-A619-7FB78B48513D@ipfire.org>
[-- 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
> >
>
>
next prev parent reply other threads:[~2019-05-23 12:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-23 12:12 ummeegge
2019-05-23 12:13 ` Michael Tremer
2019-05-23 12:30 ` ummeegge [this message]
2019-05-23 12:31 ` Michael Tremer
2019-05-23 12:41 ` ummeegge
2019-05-23 12:56 ` ummeegge
2019-05-23 17:47 ` ummeegge
2019-05-24 5:37 ` ummeegge
2019-05-26 15:05 ` ummeegge
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f087df6467ac467f2a65b7c2857b1d45d8e9d219.camel@ipfire.org \
--to=ummeegge@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox