Talk:Community Jabber Servers: Difference between revisions
(updated shell script regex and added test snippet to avoid more instances of bert's frustration) |
No edit summary |
||
(3 intermediate revisions by 2 users not shown) | |||
Line 48: | Line 48: | ||
</nowiki> |
</nowiki> |
||
</pre> |
</pre> |
||
== Still 150 user limited? == |
|||
The page mentions a scalability limit of 150 users per server, is this still applicable? --[[User:Quozl|Quozl]] 22:27, 21 October 2014 (UTC) |
|||
:: Not that I know of -- I don't know where that number came from. I will remove it. [[User:MartinDengler|MartinDengler]] 23:58, 21 October 2014 (UTC) |
|||
::: Thanks. --[[User:Quozl|Quozl]] 00:14, 22 October 2014 (UTC) |
Latest revision as of 00:14, 22 October 2014
is xochat still down? --HarperReed 03:29, 2 March 2008 (EST)
- Yes. I must look into an issue Tom Hoffman's having in deleting the old data... Quickest way to check if it's up: nc xochat.org 5222 --morgs 08:47, 3 March 2008 (EST)
- Let me know if he needs hosting. It would be a shame to lose such good name. We might be able to split it up by regions as well. like chi.xochat.org, nyc.xochat.org or whatever. i am not sure if he would be into it - but it would be great to resurrect it at least.--HarperReed 11:12, 3 March 2008 (EST)
There have been a report by Sjackman that xochat.org was down on 4/19. Has anyone else experienced this? It is up for me, but there easily could be a bug. Thanks. --HarperReed 03:41, 19 April 2008 (EDT)
- Yes, xochat.org is definitely down on 20080901. MartinDengler 19:31, 2 September 2008 (UTC)
build 650 uses port 5223; UP list incomplete
MartinDengler: Please review: XO's (build 650) use legacy port 5223 not 5222, which you used. You are missing Jabbers set for XO's only. -- 24.236.234.244
- Thanks - the list is complete now and I've updated the little script. MartinDengler 08:55, 8 September 2008 (UTC)
The script reports all servers are down today - can that be true? Bert 12:01, 14 October 2008 (UTC)
- Never mind. I had to install python-xmpp for the script to work - it's a bit unfortunate that all error output is supressed Bert 14:23, 14 October 2008 (UTC)
- Yeah, tedious. MartinDengler 22:18, 4 December 2008 (UTC)
Server checking script
This xmpp_alive.py script will check all the servers on this Community Server page and report if they're up:
#!/usr/bin/python import socket, sys socket.setdefaulttimeout(5.0) from xmpp import * success = None def test_alive(server, port): retval = None try: cl = Client(server) retval = cl.connect(server=(server, port)) except (ValueError, StreamError), msg: if isinstance(msg, (ValueError, HostGone, RemoteConnectionFailed, UndefinedCondition)): retval = False else: retval = True return retval success = test_alive(sys.argv[1], 5222) success = success or test_alive(sys.argv[1], 5223) sys.exit(0 if success else 1) #shell script $ echo "testing jabber.sugarlabs.org" ; ./xmpp_alive.py jabber.sugarlabs.org $ (for name in $(curl http://wiki.laptop.org/go/Community_Jabber_Servers 2> /dev/null| grep "^<td>.*\(\.com\|\.org\|\.biz\|\.us\|\.de\|\.edu\)" | perl -npe 's/<td>\s*(<a[^>]+>)?\s*([^<]+)\s*(<\/a>)?\s*<\/td>.*/\2/' | sort | uniq) ; do echo -n $name... ; if (./xmpp_alive.py $name > /dev/null 2>&1) ; then echo "up" ; else echo "down" ; fi ; done)
Still 150 user limited?
The page mentions a scalability limit of 150 users per server, is this still applicable? --Quozl 22:27, 21 October 2014 (UTC)
- Not that I know of -- I don't know where that number came from. I will remove it. MartinDengler 23:58, 21 October 2014 (UTC)
- Thanks. --Quozl 00:14, 22 October 2014 (UTC)