After having an incident in which I overwrote some config files,
on 10/11/2024 and updated Synchronet 3.20 files.

These errors are occurring using a custom shell also. will test with synchronet classic, and post if different.

The following problems have popped up.

1)
bullseye bulletin looks for bullseye.asc in text/menu which isn't
present, as I'm using symlinks and let it build the menu. When
i hit return, the screen clears and the Bullesye Bulletin Menu
is displayed without any further issues.

Calling Bullseye Bulletin

Synchronet BullsEye! Version 3.00 by Rob Swindell

!ERROR checking /sbbs/text/menu/bullseye.asc

The sysop has been notified.
[Hit a key]

Error log shows:
Sun Oct 13 00:37:04 2024 master/964df0f48 toolazy.synchro.net
term Node 2 <Amessyroom> !ERROR in prntfile.cpp line 287 (menu) checking "/sbbs /text/bullseye.asc" access=0


2) I added calls to sendmail.js to try and page me via
email to SMS gateway. This worked before 10/11/2024.

paging sysop calls sendmail.js (per local configuration
in chat.ini)

chat.ini:cmd=?sendmail.js -s "BBS: Someone wants to chat" -- XXXXXXXXXX@txt.att .net < /home/sbbs/ctrl/pageme
chat.ini:cmd=?sendmail.js -s "BBS: Someone wants to chat" -- XXXXXXXXXX@txt.att .net < /home/sbbs/ctrl/pageme

says it cannot compile. 1st line is a she-bang !# to jsexec
is that the correct way the file should be ?

Paging Amessyroom...!JavaScript sendmail.js line 1: SyntaxError: illegal charac t
er

!ERROR compiling /sbbs/exec/sendmail.js

The sysop has been notified.
Sat Oct 12 2024 07:42 pm Amessyroom paged you to chat from node 1

The sysop has been notified.
[Hit a key]

head /home/sbbs/repo/exec/sendmail.js
#!/sbbs/exec/jsexec -x
// Change previous line to correct jsexec path!

// Suitable as a replacement for /usr/sbin/sendmail
// and/or /usr/bin/mail
// and/or /usr/bin/mailx

var log = new File(system.temp_dir + "sendmail.log");
//log.open('a');
log.writeln(system.timestr() + ' ' + js.exec_file + ' argv=' + argv);


The error log shows:
term Node 1 !ERROR 2 (No such file or directory) in exec.cpp line 649 (js_execf ile) compiling "/sbbs/exec/sendmail.js" access=0

/sbbs is a symlink

/sbbs/exec/sendmail.js does exist

[sbbs@vmi1943160 notes]$ ls -l /sbbs
lrwxrwxrwx 1 root root 10 Jun 17 20:34 /sbbs -> /home/sbbs
[sbbs@vmi1943160 notes]$ ls -l /sbbs/exec/sendmail.js
-rwxr-xr-x 1 sbbs sbbs 3874 Jun 17 20:14 /sbbs/exec/sendmail.js [sbbs@vmi1943160 notes]$

----

After loading a theme with jpg image that has to be converted to sixel.
I'm getting the following error.

!ERROR checking /sbbs/mods/../xtrn/DigDist/DDLoginMatrixThemes/bordeaux-tower/L o
ginBackground.asc

Error log shows:

Sun Oct 13 01:15:55 2024 master/964df0f48 toolazy.synchro.net
term Node 2 !ERROR in prntfile.cpp line 287 (menu) checking "/sbbs/mods/../xtrn /DigDist/DDLoginMatrixThemes/bordeaux-tower/LoginBackground.asc" access=0
--
Amessyroom - Sysop
toolazy.synchro.net:22 (ssh)
toolazy.synchro.net:2323 (telnet)
https://toolazy.synchro.net
---
þ Synchronet þ Too Lazy BBS - toolazy.synchro.net:2323
--- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Problems after recent update of sychronet 3.20 files
By: Amessyroom to All on Sun Oct 13 2024 01:30 am

After having an incident in which I overwrote some config files, on 10/11/2024 and updated Synchronet 3.20 files.

These errors are occurring using a custom shell also. will test with synchronet classic, and post if different.

Tested with synchronet classic shell and same errors occurred on my bbs.


...Between two evils, I always pick the one I never tried before.
--
Amessyroom - Sysop
toolazy.synchro.net:22 (ssh)
toolazy.synchro.net:2323 (telnet)
https://toolazy.synchro.net
---
þ Synchronet þ Too Lazy BBS - toolazy.synchro.net:2323
--- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Problems after recent update of sychronet 3.20 files
By: Amessyroom to All on Sun Oct 13 2024 01:30 am

After having an incident in which I overwrote some config files,
on 10/11/2024 and updated Synchronet 3.20 files.

These errors are occurring using a custom shell also. will test with synchronet classic, and post if different.

The following problems have popped up.

1)
bullseye bulletin looks for bullseye.asc in text/menu which isn't
present, as I'm using symlinks and let it build the menu. When
i hit return, the screen clears and the Bullesye Bulletin Menu
is displayed without any further issues.

Calling Bullseye Bulletin

Synchronet BullsEye! Version 3.00 by Rob Swindell

!ERROR checking /sbbs/text/menu/bullseye.asc

The sysop has been notified.
[Hit a key]

Error log shows:
Sun Oct 13 00:37:04 2024 master/964df0f48 toolazy.synchro.net
term Node 2 <Amessyroom> !ERROR in prntfile.cpp line 287 (menu) checking "/sbbs /text/bullseye.asc" access=0

This should be fixed now. Previously, for a while now in v3.20a, failed calls to menu() were just silent failures. That's been fixed. So that's now highlight another (long-standing) issue when display files in "text" (rather than text/menu) and that your script's setting of the global "menu_dir" caused to fail. This should be fixed now (we won't use the global "menu_dir" as a sub-dir of text/menu when the menu "code" being displayed starts with '.' (as in, "../bullseye.asc").

2) I added calls to sendmail.js to try and page me via
email to SMS gateway. This worked before 10/11/2024.

paging sysop calls sendmail.js (per local configuration
in chat.ini)

chat.ini:cmd=?sendmail.js -s "BBS: Someone wants to chat" -- XXXXXXXXXX@txt.att .net < /home/sbbs/ctrl/pageme
chat.ini:cmd=?sendmail.js -s "BBS: Someone wants to chat" -- XXXXXXXXXX@txt.att .net < /home/sbbs/ctrl/pageme

says it cannot compile. 1st line is a she-bang !# to jsexec
is that the correct way the file should be ?

Paging Amessyroom...!JavaScript sendmail.js line 1: SyntaxError: illegal charac t
er

!ERROR compiling /sbbs/exec/sendmail.js

The sysop has been notified.
Sat Oct 12 2024 07:42 pm Amessyroom paged you to chat from node 1

The sysop has been notified.
[Hit a key]

head /home/sbbs/repo/exec/sendmail.js
#!/sbbs/exec/jsexec -x
// Change previous line to correct jsexec path!

// Suitable as a replacement for /usr/sbin/sendmail
// and/or /usr/bin/mail
// and/or /usr/bin/mailx

var log = new File(system.temp_dir + "sendmail.log");
//log.open('a');
log.writeln(system.timestr() + ' ' + js.exec_file + ' argv=' + argv);

The error log shows:
term Node 1 !ERROR 2 (No such file or directory) in exec.cpp line 649 (js_execf ile) compiling "/sbbs/exec/sendmail.js" access=0

/sbbs is a symlink

/sbbs/exec/sendmail.js does exist

[sbbs@vmi1943160 notes]$ ls -l /sbbs
lrwxrwxrwx 1 root root 10 Jun 17 20:34 /sbbs -> /home/sbbs
[sbbs@vmi1943160 notes]$ ls -l /sbbs/exec/sendmail.js
-rwxr-xr-x 1 sbbs sbbs 3874 Jun 17 20:14 /sbbs/exec/sendmail.js [sbbs@vmi1943160 notes]$

No recent changes to that script or jseexc. I'm still using sendmail.js (via jsexec) successfully on my BBS.

After loading a theme with jpg image that has to be converted to sixel.
I'm getting the following error.

!ERROR checking /sbbs/mods/../xtrn/DigDist/DDLoginMatrixThemes/bordeaux-tower/L o ginBackground.asc

Error log shows:

Sun Oct 13 01:15:55 2024 master/964df0f48 toolazy.synchro.net
term Node 2 !ERROR in prntfile.cpp line 287 (menu) checking "/sbbs/mods/../xtrn /DigDist/DDLoginMatrixThemes/bordeaux-tower/LoginBackground.asc" access=0

Does that file exist? The DDLoginMatrix may need to use the P_NOERROR flag in calls to menu() if they don't want failures to be reported as errors.
--
digital man (rob)

Rush quote #86:
Follow men's eyes as they look to the skies .. Jacob's Ladder
Norco, CA WX: 60.6øF, 72.0% humidity, 0 mph E wind, 0.00 inches rain/24hrs
--- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Problems after recent update of sychronet 3.20 files
By: Amessyroom to All on Sun Oct 13 2024 01:50 am

Tested with synchronet classic shell and same errors occurred on my bbs.

Not happening here, so I do suspect your command shell script is involved (for the bullseye.asc error anyway). But try updating to the latest before testing again. If you intentionally deleted text/bullseye.asc, then yeah, you'd get that error with any command shell. And that's now been fixed in bullseye.js.
--
digital man (rob)

Sling Blade quote #5:
Karl Childers (to father): You ought not killed my little brother...
Norco, CA WX: 60.6øF, 72.0% humidity, 0 mph E wind, 0.00 inches rain/24hrs
--- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Problems after recent update of sychronet 3.20 files
By: Digital Man to Amessyroom on Sun Oct 13 2024 02:36 am

(for the bullseye.asc error anyway). But try updating to the latest before testing again. If you intentionally deleted text/bullseye.asc, then yeah, you'd get that error with any command shell. And that's now been fixed in bullseye.js. --
digital man (rob)

Updated. But still see problem.
[sbbs@vmi1943160 notes]$ grep bull 20241013-rebuild.log
exec/bullseye.js | 4 +-
[sbbs@vmi1943160 notes]$ cd $HOME/exec
[sbbs@vmi1943160 exec]$ ls -l bullseye.js
-rw-r--r-- 1 sbbs sbbs 1895 Oct 13 10:30 bullseye.js
[sbbs@vmi1943160 exec]$ date
Sun Oct 13 10:57:38 AM EDT 2024
--
Amessyroom - Sysop
toolazy.synchro.net:22 (ssh)
toolazy.synchro.net:2323 (telnet)
https://toolazy.synchro.net
---
þ Synchronet þ Too Lazy BBS - toolazy.synchro.net:2323
--- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Problems after recent update of sychronet 3.20 files
By: Amessyroom to Digital Man on Sun Oct 13 2024 10:59 am

Updated. But still see problem.

Can you paste the error message(s) again?
--
digital man (rob)

Synchronet/BBS Terminology Definition #8:
BinkP = BinkD Protocol
Norco, CA WX: 75.5øF, 45.0% humidity, 3 mph SW wind, 0.00 inches rain/24hrs
--- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Problems after recent update of sychronet 3.20 files
By: Digital Man to Amessyroom on Sun Oct 13 2024 02:34 am

!ERROR in prntfile.cpp line 287 (menu) checking "/sbbs/mods/../xtrn
/DigDist/DDLoginMatrixThemes/bordeaux-tower/LoginBackground.asc" access=0

Does that file exist? The DDLoginMatrix may need to use the P_NOERROR flag in calls to menu() if they don't want failures to be reported as errors.

I do want those reported as errors. I think what may be happening is that DDLoginmatrix is unable to find the file to be used for the background (LoginBackground.asc in this case), perhaps because the theme is configured to look for that filename, or it's supposed to convert an image to sixel format and that's failing (and it's defaulting to .asc) - either way, it may indicate something needs to be fixed.

Nightfox

---
þ Synchronet þ Digital Distortion: digitaldistortionbbs.com
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Problems after recent update of sychronet 3.20 files
By: Nightfox to Digital Man on Sun Oct 13 2024 01:15 pm

Re: Problems after recent update of sychronet 3.20 files
By: Digital Man to Amessyroom on Sun Oct 13 2024 02:34 am

!ERROR in prntfile.cpp line 287 (menu) checking "/sbbs/mods/../xtrn
/DigDist/DDLoginMatrixThemes/bordeaux-tower/LoginBackground.asc" access=0

Does that file exist? The DDLoginMatrix may need to use the P_NOERROR flag in calls to menu() if they don't want failures to be reported as errors.

I do want those reported as errors. I think what may be happening is that DDLoginmatrix is unable to find the file to be used for the background (LoginBackground.asc in this case), perhaps because the theme is configured to look for that filename, or it's supposed to convert an image to sixel format and that's failing (and it's defaulting to .asc) - either way, it may indicate something needs to be fixed.

Okay, it's good that menu() failures are now logged as errors then. For the longest time, menu() failures would be logged, but not as errors, and then a few years back I accdientally introduced a bug that just silenced all menu() failures. That's now fixed and I'm using the normal sbbs_t::errormsg() function to log the details.
--
digital man (rob)

Synchronet "Real Fact" #48:
Synchronet directory naming (i.e. ctrl, exec, data) was suggested by S. Deppe Norco, CA WX: 77.2øF, 41.0% humidity, 4 mph W wind, 0.00 inches rain/24hrs
--- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Problems after recent update of sychronet 3.20 files
By: Amessyroom to Digital Man on Sun Oct 13 2024 10:59 am

Found issue with bullseye.js, for unknown reasons I had a copy in my mods directory. Argh.

Now to figure out the other issues.
--
Amessyroom - Sysop
toolazy.synchro.net:22 (ssh)
toolazy.synchro.net:2323 (telnet)
https://toolazy.synchro.net
---
þ Synchronet þ Too Lazy BBS - toolazy.synchro.net:2323
--- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Problems after recent update of sychronet 3.20 files
By: Digital Man to Amessyroom on Sun Oct 13 2024 01:10 pm

Re: Problems after recent update of sychronet 3.20 files By: Amessyroom to Digital Man on Sun Oct 13 2024 10:59 am

Updated. But still see problem.

Can you paste the error message(s) again? --
digital man (rob)

Synchronet/BBS Terminology Definition #8: BinkP = BinkD Protocol

I wasn't seeing the fix, because I had a copy of bullseye.js in "mods". .Possibly when you first implemented the use of files, to generate the menu.
I may have copied it to mods before, I did a fully update.

Once I removed the one from mods, then the latest download worked without the error message.
Sun Oct 13 13:34:05 2024 master/639781e2a toolazy.synchro.net
term Node 1 <Amessyroom> !ERROR in prntfile.cpp line 287 (menu) checking "/sbbs/text/bullseye.asc" access=0
--
Amessyroom - Sysop
toolazy.synchro.net:22 (ssh)
toolazy.synchro.net:2323 (telnet)
https://toolazy.synchro.net
---
þ Synchronet þ Too Lazy BBS - toolazy.synchro.net:2323
--- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Problems after recent update of sychronet 3.20 files
By: Digital Man to Amessyroom on Sun Oct 13 2024 02:34 am

2) I added calls to sendmail.js to try and page me via
email to SMS gateway. This worked before 10/11/2024.

paging sysop calls sendmail.js (per local configuration
in chat.ini)

chat.ini:cmd=?sendmail.js -s "BBS: Someone wants to chat" -- XXXXXXXXXX@txt.att .net < /home/sbbs/ctrl/pageme chat.ini:cmd=?sendmail.js -s "BBS: Someone wants to chat" -- XXXXXXXXXX@txt.att .net < /home/sbbs/ctrl/pageme

says it cannot compile. 1st line is a she-bang !# to jsexec
is that the correct way the file should be ?

Paging Amessyroom...!JavaScript sendmail.js line 1: SyntaxError: illegal charac t
er

!ERROR compiling /sbbs/exec/sendmail.js

Back to this issue: I don't believe this ever worked. sendmail.js is only designed to be run from jsexec (not from sbbs). I would expect sendmail.js to fail in exactly this way if configured like you showed in chat.ini.

So, maybe you just never tested this before? sendmail.js when used as intended (invoked from a *nix shell which in turn uses jsexec to execute the script) still works as it always has.

If you want to send an email or netmail from SBBS, the proper script to invoke would be postmsg.js, not sendmail.js.
--
digital man (rob)

Breaking Bad quote #20:
So who's your chief, little injun? - Hank Schrader
Norco, CA WX: 59.0øF, 90.0% humidity, 2 mph WNW wind, 0.00 inches rain/24hrs --- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Problems after recent update of sychronet 3.20 files
By: Digital Man to Amessyroom on Mon Oct 14 2024 11:49 pm

Back to this issue: I don't believe this ever worked. sendmail.js is only designed to be run from jsexec (not from sbbs). I would expect sendmail.js to fail in exactly this way if configured like you showed in chat.ini.

So, maybe you just never tested this before? sendmail.js when used as intended (invoked from a *nix shell which in turn uses jsexec to execute the script) still works as it always has.

If you want to send an email or netmail from SBBS, the proper script to invoke would be postmsg.js, not sendmail.js.
--

I'll give that a try, I have received text messages this way. So it is confusing. I think you are probably correct (as always), so I will see
what I can do with postmsg.js and let you know if it works for me.

Thanks.
--
Amessyroom - Sysop
toolazy.synchro.net:22 (ssh)
toolazy.synchro.net:2323 (telnet)
https://toolazy.synchro.net
--- SBBSecho 3.20-Linux
* Origin: Too Lazy BBS - toolazy.synchro.net:2323 (1:3634/58)

Re: Problems after recent update of sychronet 3.20 files
By: Errol Casey to Digital Man on Tue Oct 15 2024 03:53 pm

I'll give that a try, I have received text messages this way. So it is confusing. I think you are probably correct (as always), so I will see
what I can do with postmsg.js and let you know if it works for me.

sendmail.js just can't (and never could) be invoked in that way. There are multiple reasons why this would never work, but one obvious thing is that command-lines beginning with a '?' just go directly into the linked JavaScript engine (and not passed to any OS command shell), so the file indirection you're using on that command line (via the '<' operator) would never work. Plus, like you've already pointed out, that first line in sendmail.js means it can't be invoked directly via SBBS. So... yeah, it never worked the way you show it configured.
--
digital man (rob)

Sling Blade quote #25:
Karl: they seen fit to put me in here and here I've been a great long while. Norco, CA WX: 68.1øF, 73.0% humidity, 4 mph WSW wind, 0.00 inches rain/24hrs --- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)