[SOLVED]: Meteor and Realtime: no posting appears in main timeline

Moe

Hi gurus :)

My first posting is about my tries to get Meteor and Realtime running (and my fail), but first the facts:
- StatusNet is installed on an internal web server (dedicated host system)
- One IP address: 10.149.106.31 (it is a company internal address), DNS is working
- StatusNet 0.9.7fix1
- Meteo was d/led yesterday, so actual version
- scripts/startdaemons.sh was called, can be seen in ps ax
- System is Debian / Ubuntu (I tried it on two systems for tests)

This is my netstat:
tcp 0 0 10.149.106.31:4670 0.0.0.0:* LISTEN 1000 973998 18325/meteord daemo
tcp 0 0 127.0.0.1:4671 0.0.0.0:* LISTEN 1000 973997 18325/meteord daemo

:4670/meteor.js looks like this (I think that's the most important part:
mode: "stream",
pingtimeout: 20000,
pingtimer: null,
pollfreq: 3000,
port: 4670,
polltimeout: 30000,

Connected to meteor control port after sending a post (logged in as 'jim') with another browser (Konqueror in this case) shows:
LISTCHANNELS
OK
all-jim(1/0)
public(1/0)
showstream-jim(1/0)
--EOT--

Well, here is my config.php:
$config['queue']['enabled'] = true;
AddPlugin('Meteor', array(
'webserver' => 'internal.mycompany.com',
'webport' => 4670,
'channelbase' => '',
'controlserver' => '127.0.0.1',
'controlport' => 4671
));
AddPlugin('Realtime');

So it seems as if there are postings in the queue.
I also can see the "pause" and "popup" button in the main timeline (using Firefox in this case) and there seems reloading in the browser tab (the tab goes red).
Unfortunately there is no new post; it seems I did a major mistake in configuration but cannot find it.

Any help is appreciated. If you need more information, please tell me.

Thanks and regards,
Moe

jordanc

@Moe take a look at this post, gol10dr has done a pretty good write up on making meteor work on the same server.
http://forum.status.net/discussion/933/how-to-setup-a-meteor-server-on-the-same-server-as-the-webserver/

Moe

Hi jordan,

thanks for your reply.

The problem I have is that I really read the posting. Otherwise I would not know how to give information for this/an issue ;)
Maybe I should trace the traffic from/to ports 4670 and 4671.

But wait...something is different:
Telnetting to 4670 and trying to GET the queue results in only the http header. But I will check that with some JS snippets...

Thanks anyway,
Moe :)

Moe

Well, new day, new ideas. To keep it short:
After changing Meteor.joinChannel(b,0) in plugins/Meteor/meteorupdater.min.js to Meteor.joinChannel(b,1) (and similar in plugins/Meteor/meteorupdater.js to be sure), everything works nearly perfectly ;) (It seems there might be a problem concerning deleted postings, but maybe that's another problem....)

I hope this "workaround" helps the developers of StatusNet :)

Best,
Moe