Re: Core120 update problem

Re: Core120 update problem

[Michael Tremer]

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

Hello,

on my system I have only rolled out the system libraries but I have not updated
any add-ons, yet. So cannot tell.

I don't really understand what the problem is that tor doesn't work. Does it not
start? Does it crash? What does it do?

The perl warnings from the CGI shouldn't stop the daemon from working.

Best,
-Michael

On Wed, 2018-02-28 at 18:36 +0100, ummeegge wrote:
> Hi all,
> am testing currently the origin/next with u.a. the updated OpenSSL-
> 1.1.0g and wanted to report an issue with Tor.
> 
> Tor can not be started, messages do not report something but have found
> in error_log:
> 
> [Wed Feb 28 18:24:42 2018] tor.cgi: Scalar value @pid[0] better written as
> $pid[0] at /srv/web/ipfire/cgi-bin/tor.cgi line 238.
> [Wed Feb 28 18:24:42 2018] tor.cgi: Scalar value @pid[0] better written as
> $pid[0] at /srv/web/ipfire/cgi-bin/tor.cgi line 247.
> [Wed Feb 28 18:24:42 2018] tor.cgi: "my" variable @cmds masks earlier
> declaration in same scope at /srv/web/ipfire/cgi-bin/tor.cgi line 952.
> [Wed Feb 28 18:24:42 2018] tor.cgi: Name "Header::colourgreen" used only once:
> possible typo at /srv/web/ipfire/cgi-bin/tor.cgi line 242.
> [Wed Feb 28 18:24:42 2018] tor.cgi: Name "Header::colourorange" used only
> once: possible typo at /srv/web/ipfire/cgi-bin/tor.cgi line 568.
> [Wed Feb 28 18:24:42 2018] tor.cgi: Name "Header::colouryellow" used only
> once: possible typo at /srv/web/ipfire/cgi-bin/tor.cgi line 35.
> 
> Addon 'tor' not found.
> 
> addonctrl addon (start|stop|restart|reload|status|enable|disable)
> 
> [Wed Feb 28 18:24:43 2018] tor.cgi: Use of uninitialized value $pid[0] in
> concatenation (.) or string at /srv/web/ipfire/cgi-bin/tor.cgi line 80.
> [Wed Feb 28 18:24:43 2018] tor.cgi: Use of uninitialized value in addition (+)
> at /srv/web/ipfire/cgi-bin/tor.cgi line 85.
> 
> Addon 'tor' not found.
> 
> addonctrl addon (start|stop|restart|reload|status|enable|disable)
> 
> [Wed Feb 28 18:24:44 2018] tor.cgi: Use of uninitialized value $pid[0] in
> concatenation (.) or string at /srv/web/ipfire/cgi-bin/tor.cgi line 80.
> [Wed Feb 28 18:24:44 2018] tor.cgi: Use of uninitialized value in addition (+)
> at /srv/web/ipfire/cgi-bin/tor.cgi line 85.
> 
> 
> Since tor is an addon i did installed it of course from Core 120 dev
> environment.
> 
> -> tor -v
> Feb 28 18:35:20.633 [notice] Tor 0.3.2.9 (git-9e8b762fcecfece6) running on
> Linux with Libevent 2.1.8-stable, OpenSSL 1.1.0g, Zlib 1.2.11, Liblzma 5.2.3,
> and Libzstd N/A.
> Feb 28 18:35:20.633 [notice] Tor can't help you if you use it wrong! Learn how
> to be safe at https://www.torproject.org/download/download#warning
> Feb 28 18:35:20.633 [warn] Command-line option '-v' with no value. Failing.
> Feb 28 18:35:20.633 [err] Reading config failed--see warnings above.
> 
> 
> It might be great if someone can double check this.
> 
> Greetings,
> 
> Erik

Re: Core120 update problem

[ummeegge]

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

Hi Michael,

Am Donnerstag, den 01.03.2018, 21:03 +0000 schrieb Michael Tremer:
> Hello,
> 
> on my system I have only rolled out the system libraries but I have
> not updated
> any add-ons, yet. So cannot tell.
> 
> I don't really understand what the problem is that tor doesn't work.
> Does it not
> start? Does it crash? What does it do?
Did a fresh install of Core 120 with state of last commit
ca4c354e085083dacf66071b23e507ea2ebb1b81 on a pysical machine, 
loaded tor from packages dir installed it via install.sh from
/opt/pakfire/tmp and simply tried to start it via tor.cgi (enabled it
via checkbox, without tor relay) pressed the 'save' button but it
appears to be 'STOPPED' in WUI. Checked then messages but find nothing
(no tor messages), the only hint was in httpd/error_log .

The "Addon 'tor' not found." message seems likewise strange to me too,
currently not sure what happens there.

> 
> The perl warnings from the CGI shouldn't stop the daemon from
> working.
> 
> Best,
> -Michael
> 
> On Wed, 2018-02-28 at 18:36 +0100, ummeegge wrote:
> > 
> > Hi all,
> > am testing currently the origin/next with u.a. the updated OpenSSL-
> > 1.1.0g and wanted to report an issue with Tor.
> > 
> > Tor can not be started, messages do not report something but have
> > found
> > in error_log:
> > 
> > [Wed Feb 28 18:24:42 2018] tor.cgi: Scalar value @pid[0] better
> > written as
> > $pid[0] at /srv/web/ipfire/cgi-bin/tor.cgi line 238.
> > [Wed Feb 28 18:24:42 2018] tor.cgi: Scalar value @pid[0] better
> > written as
> > $pid[0] at /srv/web/ipfire/cgi-bin/tor.cgi line 247.
> > [Wed Feb 28 18:24:42 2018] tor.cgi: "my" variable @cmds masks
> > earlier
> > declaration in same scope at /srv/web/ipfire/cgi-bin/tor.cgi line
> > 952.
> > [Wed Feb 28 18:24:42 2018] tor.cgi: Name "Header::colourgreen" used
> > only once:
> > possible typo at /srv/web/ipfire/cgi-bin/tor.cgi line 242.
> > [Wed Feb 28 18:24:42 2018] tor.cgi: Name "Header::colourorange"
> > used only
> > once: possible typo at /srv/web/ipfire/cgi-bin/tor.cgi line 568.
> > [Wed Feb 28 18:24:42 2018] tor.cgi: Name "Header::colouryellow"
> > used only
> > once: possible typo at /srv/web/ipfire/cgi-bin/tor.cgi line 35.
> > 
> > Addon 'tor' not found.
> > 
> > addonctrl addon (start|stop|restart|reload|status|enable|disable)
> > 
> > [Wed Feb 28 18:24:43 2018] tor.cgi: Use of uninitialized value
> > $pid[0] in
> > concatenation (.) or string at /srv/web/ipfire/cgi-bin/tor.cgi line
> > 80.
> > [Wed Feb 28 18:24:43 2018] tor.cgi: Use of uninitialized value in
> > addition (+)
> > at /srv/web/ipfire/cgi-bin/tor.cgi line 85.
> > 
> > Addon 'tor' not found.
> > 
> > addonctrl addon (start|stop|restart|reload|status|enable|disable)
> > 
> > [Wed Feb 28 18:24:44 2018] tor.cgi: Use of uninitialized value
> > $pid[0] in
> > concatenation (.) or string at /srv/web/ipfire/cgi-bin/tor.cgi line
> > 80.
> > [Wed Feb 28 18:24:44 2018] tor.cgi: Use of uninitialized value in
> > addition (+)
> > at /srv/web/ipfire/cgi-bin/tor.cgi line 85.
> > 
> > 
> > Since tor is an addon i did installed it of course from Core 120
> > dev
> > environment.
> > 
> > -> tor -v
> > Feb 28 18:35:20.633 [notice] Tor 0.3.2.9 (git-9e8b762fcecfece6)
> > running on
> > Linux with Libevent 2.1.8-stable, OpenSSL 1.1.0g, Zlib 1.2.11,
> > Liblzma 5.2.3,
> > and Libzstd N/A.
> > Feb 28 18:35:20.633 [notice] Tor can't help you if you use it
> > wrong! Learn how
> > to be safe at https://www.torproject.org/download/download#warning
> > Feb 28 18:35:20.633 [warn] Command-line option '-v' with no value.
> > Failing.
> > Feb 28 18:35:20.633 [err] Reading config failed--see warnings
> > above.
> > 
> > 
> > It might be great if someone can double check this.
> > 
> > Greetings,
> > 
> > Erik


It might be helpful if someone who installed/testing Core 120 too can
go for a checkout on that so we can be aware that this is not a
individual one.

Greetings,

Erik

Re: Core120 update problem

[ummeegge]

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

Hi all,
fast feedback causing this topic, have build tor-0.3.3.2-alpha which
worked without problems, have then seen that tor-0.3.2.10 has also been
released, have build it and tested it too in Core 120 environment and
it starts and seems also to work again without problems.

Greetings,

UE