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.
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
Tested with synchronet classic shell and same errors occurred on my bbs.
(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.
!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.
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.
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
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.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
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.
| Sysop: | Cryptfiend |
|---|---|
| Location: | Tampa, FL |
| Users: | 3 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 42:51:07 |
| Calls: | 103 |
| Messages: | 10,562 |