Reposting this for the third time. Hopefully this one goes through:

I'm setting up two peers *on the same box*.

Peer 1:
running nntp port 119/nntp-ssl port 563
remote_peer: 127.0.0.1
remote_port: 120
remote_ssl: 564

Peer 2:
running nntp 120/nntp-ssl 564
remote_peer: 127.0.0.1
remote_port: 119
remote_ssl: 563

when I run cron, it calls send.php, which calls newsportal->nntp2_open() to create a new socket for sending remote posts. It fails to open a socket, and dies there without any error message. fsockopen reports exit(0) which is "i couldn't failed to open a socket, so there isn't a real error message".

is this because i've got an obvious error in my configuration as posted above, or am I trying to do something obviously dumb in trying to run two tomo/RSL servers on the same machine?

fwiw, both servers post & read absolutely fine. it's just the remote peering that's causing it to choke.

--
Posted on Rocksolid Light

vga256 wrote:

> Reposting this for the third time. Hopefully this one goes through:

> I'm setting up two peers *on the same box*.

> Peer 1:
> running nntp port 119/nntp-ssl port 563
> remote_peer: 127.0.0.1
> remote_port: 120
> remote_ssl: 564

> Peer 2:
> running nntp 120/nntp-ssl 564
> remote_peer: 127.0.0.1
> remote_port: 119
> remote_ssl: 563

Interesting. I have not tried to do that. Can you telnet to the ports and get the nntp server?

I HAVE run two instances on the same machine, but never tried to connect them to eachother.

I assume that 'running nntp port...' means that the peer is set up as 'local_server' for that info.

You may wish to try adding a name in /etc/hosts to separate the peer names:

127.0.0.1 tomo_peer_1 tomo_peer_2

and then using those names in your config. We may have an issue with the peer names being the same? I don't know, just trying to narrow things down.

--
Retro Guy

> Interesting. I have not tried to do that. Can you telnet to the ports and get the nntp server?

yup, no issues accessing both servers via telnet, from inside the box and from another machine on the network.

> I assume that 'running nntp port...' means that the peer is set up as 'local_server' for that info.

oops - yes, that's the local server info for both servers, on the same box.

> You may wish to try adding a name in /etc/hosts to separate the peer names:

> 127.0.0.1 tomo_peer_1 tomo_peer_2

> and then using those names in your config. We may have an issue with the peer names being the same? I don't know, just trying to narrow things down.

i don't think the issue is related to the IP not resolving. i suspect it's potentially related to fsockopen() itself, and how it handles identical ports being opened/closed simultaneously? i noticed there is a stream_set_blocking() mode that may be related.. i'll dig into it

--
Posted on Rocksolid Light

vga256 wrote:

>> You may wish to try adding a name in /etc/hosts to separate the peer names:

>> 127.0.0.1 tomo_peer_1 tomo_peer_2

>> and then using those names in your config. We may have an issue with the peer names being the same? I don't know, just trying to narrow things down.

> i don't think the issue is related to the IP not resolving. i suspect it's potentially related to fsockopen() itself, and how it handles identical ports being opened/closed simultaneously? i noticed there is a stream_set_blocking() mode that may be related.. i'll dig into it

Not so much not resolving, but being the same. But you're probably correct, it's something other than that.

I would log the server:port info being sent to nntp2_open, to verify it is trying to connect to the right place.

stream_set_blocking is for the current stream being used. It sets either blocking or non-blocking mode for the stream:

https://www.php.net/manual/en/function.stream-set-blocking.php

"If enable is false, the given stream will be switched to non-blocking mode, and if true, it will be switched to blocking mode. This affects calls like fgets() and fread() that read from the stream. In non-blocking mode an fgets() call will always return right away while in blocking mode it will wait for data to become available on the stream."

--
Retro Guy

Just realized how silly it is that I'm trying to skate uphill here ;) I'll just install MAMP on another machine and run them on separate boxes for testing.

Thanks anyway!

--
Posted on Rocksolid Light

So - interesting update: even when run on a separate server, I'm getting the same error 0 from fsockopen. At least now I've ironed out the idea of it being running on the same box (with conflicting network ports, or I/O, or who knows!) as being the issue.

--
Posted on Rocksolid Light

ah ha, turned out to be some kind of issue with SSL. I disabled the ssl port, and it's at least connecting and *says* it has sent articles. ("Send Done.")

The articles haven't actually synced between machines, but this is a step in the right direction!

--
Posted on Rocksolid Light

vga256 wrote:

> ah ha, turned out to be some kind of issue with SSL. I disabled the ssl port, and it's at least connecting and *says* it has sent articles. ("Send Done.")

> The articles haven't actually synced between machines, but this is a step in the right direction!

Sounds good so far.

I did change my local test server to use the ssl port on novabbs.org (where it syncs), and it's working fine. I made the change in nntp2_open first :)

Let's hope it's almost working.

--
Retro Guy

woohoo. got it working. turned out that i replaced bbs_user_auth with authenticate_user (which relies upon the user sqlite db), and forgot to create a localuser in the sqlite db :)

--
Posted on Rocksolid Light

vga256 wrote:

> woohoo. got it working. turned out that i replaced bbs_user_auth with authenticate_user (which relies upon the user sqlite db), and forgot to create a localuser in the sqlite db :)

Nice! Glad you have it working!

BTW, rslight autocreates the user 'localuser' based on the timestamp of the config file. It's something to consider so you don't in the future change the localuser password or something, and wonder why it's not working.

--
Retro Guy

Retro Guy wrote:

> vga256 wrote:

>> woohoo. got it working. turned out that i replaced bbs_user_auth with authenticate_user (which relies upon the user sqlite db), and forgot to create a localuser in the sqlite db :)

> Nice! Glad you have it working!

> BTW, rslight autocreates the user 'localuser' based on the timestamp of the config file. It's something to consider so you don't in the future change the localuser password or something, and wonder why it's not working.

Also, we should add logging for such an event. I'll take care of that on my end (probably in check_bbs_auth()). It should also be easy for you in your auth function.

--
Retro Guy

> BTW, rslight autocreates the user 'localuser' based on the timestamp of the config file. It's something to consider so you don't in the future change the localuser password or something, and wonder why it's not working.

can you point me in the right direction for the autocreation? I searched my sourcetree (and RSL's), and couldn't find entries related to autocreation for server_auth_user, aside from a mention in setuphelper

--
Posted on Rocksolid Light

vga256 wrote:

>> BTW, rslight autocreates the user 'localuser' based on the timestamp of the config file. It's something to consider so you don't in the future change the localuser password or something, and wonder why it's not working.

> can you point me in the right direction for the autocreation? I searched my sourcetree (and RSL's), and couldn't find entries related to autocreation for server_auth_user, aside from a mention in setuphelper

In newsportal.php, in check_bbs_auth():

if($username == strtolower($CONFIG['server_auth_user'])) {
if(filemtime($config_dir."rslight.inc.php") > filemtime($userFilename)) {
if ($userFileHandle = fopen($userFilename, 'w+'))
{
fwrite($userFileHandle, password_hash($CONFIG['server_auth_pass'], PASSWORD_DEFAULT));
fclose($userFileHandle);
}
}
}

If there is a way in your .db to know the time that the user or password was set, it should be easy, but I'm not sure you would have put that row in your table (I wouldn't have thought to do so if it were me).

Also, you'd probably want to change it to allow for a different 'server_auth_user' per section. I should change that here also.

--
Retro Guy

> If there is a way in your .db to know the time that the user or password was set, it should be easy, but I'm not sure you would have put that row in your table (I wouldn't have thought to do so if it were me).

> Also, you'd probably want to change it to allow for a different 'server_auth_user' per section. I should change that here also.

Great - thanks for the implementation.

I've made some progress. The servers are talking with one another, and they can successfully pull newsgroup posts from one another. What is not working - yet - is encrypted messaging. The messages are being created in mail, but they are not being posted to tomonet.shared.test, which has been set as the sharing group on both servers in gpg.conf.

There's a silent failure somewhere in the message creation chain, but I'm not really sure where to start looking.

--
Posted on Rocksolid Light

okay, so i've narrowed it down to a few potential problems.

can you tell me if your server is running a php module for gnupg, or if you're running gpg from the command line?

i'm getting a "Call to undefined function gnupg_init()" error when interBBS_mail runs. I imagine this is because php8.2 needs to have the gnupg module installed?

--
Posted on Rocksolid Light

vga256 wrote:

> okay, so i've narrowed it down to a few potential problems.

> can you tell me if your server is running a php module for gnupg, or if you're running gpg from the command line?

> i'm getting a "Call to undefined function gnupg_init()" error when interBBS_mail runs. I imagine this is because php8.2 needs to have the gnupg module installed?

You will need the packages (Debian names) gnupg and php-gnupg

--
Retro Guy

> You will need the packages (Debian names) gnupg and php-gnupg

ah ha ha.. i had one of the two! i'll get php-gnupg figured out tomorrow. thanks for all the help today - this has been a bit of an uphill battle.

--
Posted on Rocksolid Light

progress:
- php-gnupg installed
- gpg environment seems to be built correctly
- shared.test groups created on both sending/receiving machines

after composing a new private message (from user@bbs.tomo.city to user@tomo.dialup.cafe) and hitting send, I get:
Posted <791826e2717f384e@bbs.tomo.city> Message sent.

I check shared.test, and there are no messages posted to that group. Running cron.php makes no difference - posts from other groups are exchanged, but since there is nothing in shared.test to swap, no mail messages are exchanged between the machines.

Any ideas on where to go from here?

--
Posted on Rocksolid Light

Edit: I think I might have tracked down the issue. i checked ~/spoolnews/tomonet/outgoing/ and the messages being posted to shared.test are owned by root. I suspect some permissions shenanigans here.

--
Posted on Rocksolid Light

vga256 wrote:

> progress:
> - php-gnupg installed
> - gpg environment seems to be built correctly
> - shared.test groups created on both sending/receiving machines

> after composing a new private message (from user@bbs.tomo.city to user@tomo.dialup.cafe) and hitting send, I get:
> Posted <791826e2717f384e@bbs.tomo.city> Message sent.

> I check shared.test, and there are no messages posted to that group. Running cron.php makes no difference - posts from other groups are exchanged, but since there is nothing in shared.test to swap, no mail messages are exchanged between the machines.

> Any ideas on where to go from here?

Check /var/spool/rslight/<section>/outgoing for a mail message. This is where messages reside before being sent to remote server.

If it's there after running cron.php again, check for the filename in /var/spool/rslight/log/spoolnews.log to see if there is a comment.

Is shared.test the value of $rslight_gpg['nntp_group'] in gpg.conf?

--
Retro Guy

Alright, root ownership didn't turn out to be the issue (but it did give me the chance to fix a misconfiguration on my part).

It did help clarify one thing: i'm not getting any mail posted to either ~/spoolnews/bbsmail or ~/spoolnews/tomonet/outgoing, nor the key advertisement in tomonet.shared.test

--
Posted on Rocksolid Light

vga256 wrote:

> Edit: I think I might have tracked down the issue. i checked ~/spoolnews/tomonet/outgoing/ and the messages being posted to shared.test are owned by root. I suspect some permissions shenanigans here.

Strange, they should be owned by the web user.

--
Retro Guy

Retro Guy wrote:

> vga256 wrote:

>> progress:
>> - php-gnupg installed
>> - gpg environment seems to be built correctly
>> - shared.test groups created on both sending/receiving machines

>> after composing a new private message (from user@bbs.tomo.city to user@tomo.dialup.cafe) and hitting send, I get:
>> Posted <791826e2717f384e@bbs.tomo.city> Message sent.

>> I check shared.test, and there are no messages posted to that group. Running cron.php makes no difference - posts from other groups are exchanged, but since there is nothing in shared.test to swap, no mail messages are exchanged between the machines.

>> Any ideas on where to go from here?

> Check /var/spool/rslight/<section>/outgoing for a mail message. This is where messages reside before being sent to remote server.

> If it's there after running cron.php again, check for the filename in /var/spool/rslight/log/spoolnews.log to see if there is a comment.

> Is shared.test the value of $rslight_gpg['nntp_group'] in gpg.conf?

If the messages show up in shared.test on the target server, they should be copied to /var/spool/rslight/bbsmail/in

interBBS_mail.php will only act on them if they are found in that directory.

--
Retro Guy

> Check /var/spool/rslight/<section>/outgoing for a mail message. This is where messages reside before being sent to remote server.

that's empty - so there's some kind of silent error/failure before the message gets copied to /outgoing

> If it's there after running cron.php again, check for the filename in /var/spool/rslight/log/spoolnews.log to see if there is a comment.

no errors in spoolnews - if I manually post a message in tomonet.shared.test, it is correctly synced between servers

> Is shared.test the value of $rslight_gpg['nntp_group'] in gpg.conf?

yep, that's been configured on both servers.

--
Posted on Rocksolid Light

vga256 wrote:

> Alright, root ownership didn't turn out to be the issue (but it did give me the chance to fix a misconfiguration on my part).

> It did help clarify one thing: i'm not getting any mail posted to either ~/spoolnews/bbsmail or ~/spoolnews/tomonet/outgoing, nor the key advertisement in tomonet.shared.test

Do you have a permissions issue? Directories owned by root but trying to write as www user?

--
Retro Guy