Control: severity -1 minor
HI Stefan,
On Di 22 Mär 2016 10:54:43 CET, Stefan Baur wrote:
The reason, as I found out later, was, that it tries to bind to
127.0.0.1:8080 by default, and that port is already in use by another
process on that machine.
IMO, this is a bug: when it can't bind to
Am 22.03.2016 um 11:58 schrieb Mike Gabriel:
> Apart from the bug title, you don't provide a description about what
> your issue really is. Thus, tagging this bug with "not-a-bug".
Could it be that you only read the second e-mail belonging to this bug?
The first one was rather lengthy and
Wait ... is the step regarding the Postgres DB listed at
http://wiki.x2go.org/doku.php/wiki:advanced:x2gobroker:loadbalancing
and
http://wiki.x2go.org/doku.php/wiki:advanced:multi-node:x2goserver-pgsql
required even for the python broker?
If so:
a) Would it be possible to install the database
Hello, Sébastien!
As you might know, I'm the current X2Go Project/Community Manager, and
I'm not a coder, so I can't really judge the value of your contribution
myself - but I heard it from the other developers on previous occasions
that this was indeed a big upcoming issue, and their reaction so
Hello,
Stefan Baur wrote :
> As you might know, I'm the current X2Go Project/Community Manager, and
> I'm not a coder, so I can't really judge the value of your contribution
> myself - but I heard it from the other developers on previous occasions
> that this was indeed a big upcoming issue, and
Processing control commands:
> tags -1 not-a-bug
Bug #1012 [x2gobroker] Session reconnect doesn't work (x2gobroker)
Added tag(s) not-a-bug.
> severity -1 wishlist
Bug #1012 [x2gobroker] Session reconnect doesn't work (x2gobroker)
Severity set to 'wishlist' from 'normal'
--
1012:
Processing control commands:
> severity -1 minor
Bug #1013 [x2gobroker-daemon] x2gobroker-daemon doesn't return error when it
can't spawn/bind to port
Severity set to 'minor' from 'normal'
--
1013: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=1013
X2Go Bug Tracking System
Contact
Am 22.03.2016 um 12:01 schrieb Mike Gabriel:
>
> Yeah, this is a valid issue. Is you system launching x2gobroker-daemon
> via systemd or via System V init scripts?
This is on System V init, as we've seen SystemD misbehaving with some of
our own init scripts.
Kind Regards,
Stefan
--
BAUR-ITCS
Hi Stefan,
ah, sorry, missed your initial post around #1012.
On Di 22 Mär 2016 10:42:03 CET, Stefan Baur wrote:
package: x2gobroker
version: 0.0.3.0
Situation: two identical nodes, only difference is DNS name + IP
Desired result: load-balanced X2Go systems, where a suspended session
Control: severity -1 normal
Control: tags -1 - not-a-bug
On Di 22 Mär 2016 12:00:37 CET, Stefan Baur wrote:
Am 22.03.2016 um 11:58 schrieb Mike Gabriel:
Apart from the bug title, you don't provide a description about what
your issue really is. Thus, tagging this bug with "not-a-bug".
Could
package: x2gobroker-daemon
version: 0.0.3.0
This is what happened:
node:~# service x2gobroker-daemon stop
[] Stopping X2Go Session Broker standalone daemon:
x2gobroker-daemonstart-stop-daemon: warning: failed to kill 14170: No
such process
failed!
# huh, wait, what?
node:~# ps ax | grep
package: x2gobroker
version: 0.0.3.0
Situation: two identical nodes, only difference is DNS name + IP
Desired result: load-balanced X2Go systems, where a suspended session
can be resumed
Actual outcome: Each connect starts a new session, suspended sessions
12 matches
Mail list logo
