Howdy,
I've just discovered something weird, that has been happening for a month or two. Probably since I moved from x86_64 to aarch64.
When outbound FTN mail is created, sbbsecho is correctly placing the .?lo file in the zone oubound dir, and triggering binkit to send it.
It seems when binkit calls the remote, when it goes to open the .?lo file to see what to send, its gone. I can re-produce this pretty easily, its happening for all my FTN networks.
As a consequence, no mail gets sent.
Here is an except from syslog:
Jun 02 15:42:47 ? local1.info synchronet: evnt FIDOOUT Running native timed event: /opt/sbbs/exec/sbbsecho -ni
Jun 02 15:42:49 ? local1.info synchronet: evnt FIDOOUT Timed event: '/opt/sbbs/exec/sbbsecho -ni' returned 0
Jun 02 15:42:50 ? local1.info synchronet: evnt BBS Events Semaphore signaled for Timed Event: BINKOUT
Jun 02 15:42:50 ? local1.info synchronet: evnt BINKOUT Running native timed event: ?binkit
Jun 02 15:42:50 ? local1.info synchronet: evnt BINKOUT BinkIT/2.41 invoked with options:
Jun 02 15:42:51 ? local1.info synchronet: evnt BINKOUT Attempting callout for 12:1/1@dovenet, file: /opt/sbbs/fido/outbound.00c/00010001.dlo
Jun 02 15:42:51 ? local1.info synchronet: evnt BINKOUT JSBinkP/4 callout to 12:1/1@dovenet started
Jun 02 15:42:51 ? local1.info synchronet: evnt BINKOUT Connecting to 12:1/1@dovenet at clrghouz.bbs.dege.au:24554
Jun 02 15:43:00 ? local1.info synchronet: evnt BINKOUT Will encrypt session. Jun 02 15:43:00 ? local1.info synchronet: evnt BINKOUT Authentication successful: secure
Jun 02 15:43:28 ? local1.err synchronet: evnt BINKOUT Error 11 opening FLO file: /opt/sbbs/fido/outbound.00c/00010001.dlo
Jun 02 15:43:31 ? local1.info synchronet: evnt BINKOUT Timed event: '?binkit' returned 0
I just rebuilt sbbs today, as my last build was about a month or two old - still the same.
Why the error 11, and what would cause the file to disappear?
If I create the .?lo manually, and send it interactively with jsexec binkit -l ... , the file doesnt disappear (until the mail is sent), and the mail gets transfered correctly.
I think this is related to me switching to aarch64. I'm using the same config, and the same build process as I have always used.
Why the error 11, and what would cause the file to disappear?
/usr/include/asm-generic/errno-base.h:#define EAGAIN 11 /* Try again */
I'm guessing that means the file was opened for exclusive access or the file system was doing something with the file. It's not saying the file "is gone".
It sounds like BinkIt should peform an open-retry when getting that specific open error. Submit an issue at gitlab.synchro.net for someone to follow-up on this?
Re: .?lo files disappearing error 11
By: Digital Man to deon on Mon Jun 02 2025 02:45 pm
Howdy,
Why the error 11, and what would cause the file to disappear?
/usr/include/asm-generic/errno-base.h:#define EAGAIN 11
/* Try again */
I'm guessing that means the file was opened for exclusive access or the file system was doing something with the file. It's not saying the file "is gone".
Oh, I'm telling you the file is gone.
My outbound directory is left with a bunch of packets and no .?lo file.
If I "watch ls -al outbound.xxx/", I can see sbbsecho create the packet, create the .?lo file.
As soon as binkit goes to send it, it disappears, and the Error 11 is reported at the same time.
I have mail going out frequently (at least every hour), and it is happening every time.
"Try again" doesnt make sense for this - as the file is not there..
It sounds like BinkIt should peform an open-retry when getting that specific open error. Submit an issue at gitlab.synchro.net for someone to follow-up on this?
OK.
Most likely, BinkIt is deleting the file itself immediately after that error is logged.
I would expect to see a "Deleted file: /path/to/flo-file" log message in that case, however, and you didn't show that, so that's suspicious.
Is it possible SBBSecho or another process still has this FLO file open at that moment?
Sysop: | Tandy |
---|---|
Location: | New York, USA |
Users: | 15 |
Nodes: | 13 (0 / 13) |
Uptime: | 07:32:37 |
Calls: | 340 |
Messages: | 125,788 |