Hola Todos!
When writing a message from the BBS or from the Web (webv4) in a message area, the fidoout.now file does not appear in the data directory. This prevents the message from being exported to other nodes.
What can be happening?
In cfg->Networks>FidoNet... I have set the same semaphores in netmail and echomail: %jfidoout.now, which is what comes by default. But, as I said before, that file is not created. If I create it by hand then it does export the message correctly, ie it calls "sbbsecho -ni" to scan the messages.
Is there anything I can see more? Am I making a mistake?
Check your log output? You should see something like this:
sbbs: evnt BBS Events Semaphore signaled for Timed Event: FIDOOUT
sbbs: evnt FIDOOUT Running native timed event: FIDOOUT
sbbs: evnt FIDOOUT Executing external: /sbbs/exec/sbbsecho -linf
sbbs: evnt FIDOOUT Timed event: FIDOOUT returned 0
sbbs: evnt BBS Events Semaphore signaled for Timed Event: FIDOOUT
sbbs: evnt FIDOOUT Running native timed event: FIDOOUT
sbbs: evnt FIDOOUT Executing external: /sbbs/exec/sbbsecho -linf
sbbs: evnt FIDOOUT Timed event: FIDOOUT returned 0
sbbs: evnt BBS Events Semaphore signaled for Timed Event: FIDOOUT
sbbs: evnt FIDOOUT Running native timed event: FIDOOUT
sbbs: evnt FIDOOUT Executing external: /sbbs/exec/sbbsecho -linf
sbbs: evnt FIDOOUT Timed event: FIDOOUT returned 0
Hola Digital!
20 Jul 23 11:59, Digital Man dijo a Angel Ripoll:
sbbs: evnt BBS Events Semaphore signaled for Timed Event: FIDOOUT
sbbs: evnt FIDOOUT Running native timed event: FIDOOUT
sbbs: evnt FIDOOUT Executing external: /sbbs/exec/sbbsecho -linf
sbbs: evnt FIDOOUT Timed event: FIDOOUT returned 0
Another test:
2023-07-21T00:48:27.863647+02:00 BBS synchronet: term Node 1 <aripoll> '?fseditor /sbbs/node1/temp/INPUT.MSG' returned 0 2023-07-21T00:48:27.873252+02:00 BBS synchronet: term Node 1 <aripoll> posted to All on Local Area de pruebas
2023-07-21T00:48:39.671029+02:00 BBS synchronet: term Node 1 <aripoll> append key into keybuf: 59 (Y)
2023-07-21T00:48:41.276275+02:00 BBS synchronet: term Node 1 <aripoll> disconnecting client
2023-07-21T00:48:41.276628+02:00 BBS synchronet: term Node 1 passthru socket disconnected
2023-07-21T00:48:41.670822+02:00 BBS synchronet: term Node 1 input thread terminated (received 223 bytes in 205 blocks)
No FIDOOUT or evnt in log
Hola Digital!
21 Jul 23 00:49, Angel Ripoll dijo a Digital Man:
sbbs: evnt BBS Events Semaphore signaled for Timed Event: FIDOOUT
sbbs: evnt FIDOOUT Running native timed event: FIDOOUT
sbbs: evnt FIDOOUT Executing external: /sbbs/exec/sbbsecho -linf
sbbs: evnt FIDOOUT Timed event: FIDOOUT returned 0
I don't know if it has to do but I found this error after receiving mail:
2023-07-21T00:56:10.336019+02:00 BBS synchronet: srvc 0054 BINKP Touching semaphore file: /sbbs/data/fidoin.now
2023-07-21T00:56:10.342034+02:00 BBS synchronet: srvc 0054 BINKP service thread terminated (1 clients remain, 1 total, 15 served) 2023-07-21T00:56:11.021119+02:00 BBS synchronet: evnt BBS Events Semaphore signaled for Timed Event: FIDOIN
2023-07-21T00:56:11.021567+02:00 BBS synchronet: evnt FIDOIN Running native timed event: FIDOIN
2023-07-21T00:56:11.021775+02:00 BBS synchronet: evnt FIDOIN Executing external: /sbbs/exec/sbbsecho -ce
2023-07-21T00:56:11.031173+02:00 BBS synchronet: !setregid FAILED with error 1 (Operation not permitted)
2023-07-21T00:56:11.032190+02:00 BBS synchronet: !setreuid FAILED with error 1 (Operation not permitted)
2023-07-21T00:56:17.538198+02:00 BBS synchronet: evnt FIDOIN Timed event: FIDOIN returned 0
!setregid FAILED with error 1 (Operation not permitted)??
I do not know what that means
Is "Local Area de pruebas" configured as a FidoNet networked sub-board (in SCFG)? If not, then I wouldn't expect the fidonet echomail sem file to be touched in this scenario.
Re: Messages do not leave the BBS automatically. fidoout.now not created
By: Angel Ripoll to Digital Man on Fri Jul 21 2023 12:57 am
I think it means you have sbbs configured to change users after running, but the user you're starting sbbs as in the first place doesn't have permissions to change effective user and group IDs.
Hola Digital!
20 Jul 23 16:34, Digital Man dijo a Angel Ripoll:
Re: Messages do not leave the BBS automatically. fidoout.now not created
By: Angel Ripoll to Digital Man on Fri Jul 21 2023 12:57 am
I think it means you have sbbs configured to change users after running, but the user you're starting sbbs as in the first place doesn't have permissions to change effective user and group IDs.
It's right. I have in sbbs.ini->[UNIX] that I change the user and group to something other than root, but when i start SBBS manually with "service sbbs start" i do it with the root user and in the sbbs.service script it is root as user and group
I have to change something? Is it better to run SBBS with root user or better with another user?
It's better to start sbbs with another user: https://wiki.synchro.net/howto:linux_non-root
But it keeps getting the message that using a non-root user I may have problems with ports below 1024 but all of them are working :).
That's normal/expected. You can ignore that.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 412 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 108:54:34 |
| Calls: | 8,597 |
| Calls today: | 10 |
| Files: | 13,229 |
| Messages: | 5,935,184 |