From Newsgroup: alt.bbs.synchronet

Has there been any changes to bbs.page_sysop

Paging Amessyroom... !ERROR opening /sbbs/exec/jsexec.js The sysop has been notified. [Hit a key]

User reported it not working, and when trying to recreate noticed
the above error.

There is not a jsexec.js but a jsexec (executable) in /sbbs/exec.

Not sure if this is in js code for the command shell or c code.

Wondering if anybody else has encountered this. Redownloaded from git
and rebuilt tonight and the error continues.
---
Amessyroom
toolazy.synchro.net:2323 (telnet)
---
þ Synchronet þ Too Lazy BBS - toolazy.synchro.net:2323
--- Synchronet 3.21a-Linux NewsLink 1.2
* Vertrauen - Riverside County, California - telnet://vert.synchro.net
--- Synchronet 3.20b-Win32 NewsLink 1.2

From Newsgroup: alt.bbs.synchronet

To: Amessyroom
Re: paging sysop
By: Amessyroom to All on Mon Apr 28 2025 11:37 pm

Has there been any changes to bbs.page_sysop

Paging Amessyroom...
!ERROR opening /sbbs/exec/jsexec.js
The sysop has been notified.
[Hit a key]

User reported it not working, and when trying to recreate noticed
the above error.

There is not a jsexec.js but a jsexec (executable) in /sbbs/exec.

Not sure if this is in js code for the command shell or c code.

Wondering if anybody else has encountered this. Redownloaded from git
and rebuilt tonight and the error continues.

Check what you have configured in SCFG->Chat Features->External Sysop Chat Pagers. Sounds like you've added something there incorrectly.
--
digital man (rob)

Synchronet "Real Fact" #18:
Rob Swindell first learned to program in C by hacking on WWIV BBS software Norco, CA WX: 68.1øF, 56.0% humidity, 3 mph WSW wind, 0.00 inches rain/24hrs --- Synchronet 3.21a-Linux NewsLink 1.2
* Vertrauen - Riverside County, California - telnet://vert.synchro.net
--- Synchronet 3.20b-Win32 NewsLink 1.2

From Newsgroup: alt.bbs.synchronet

To: Amessyroom
Re: paging sysop
By: Amessyroom to Digital Man on Wed Apr 30 2025 09:12 pm

Re: paging sysop
By: Digital Man to Amessyroom on Tue Apr 29 2025 11:36 am

Re: paging sysop
By: Amessyroom to All on Mon Apr 28 2025 11:37 pm

Has there been any changes to bbs.page_sysop

Paging Amessyroom...
!ERROR opening /sbbs/exec/jsexec.js
The sysop has been notified.
[Hit a key]

User reported it not working, and when trying to recreate noticed
the above error.

There is not a jsexec.js but a jsexec (executable) in /sbbs/exec.

Not sure if this is in js code for the command shell or c code.

Wondering if anybody else has encountered this. Redownloaded from git
and rebuilt tonight and the error continues.

Check what you have configured in SCFG->Chat Features->External Sysop Chat Pagers. Sounds like you've added something there incorrectly. -- digital man (rob)

Could be but even if I clear it and try and page I get the jsexec.js error which I'm not referencing
directly.

[pager:0]
cmd=?postmsg.js -i/home/sbbs/page-message.txt -terrol -nmobilenumber@att.net -fAmessyroomn "-sUser Paging You" mail
ars=
settings=0

Is what I've tried to add in chat.ini, but it seems when viewed or edited in scfg it is truncated.

Where I sent an email to my cell #. This works manually if you do jsexec postmsg.js ....

But like I said, if there is nothing defined in chat.ini or SCFG options for external pager; selecting page still gets
error in classic synchronet command shell and my customized one.

So there still seems to be something that is triggering the call to jsexec.js which doesn't exist.

So still at a loss of how to correct the issue.

error.log shows:
term Node 1 <Daniel Garrod> !ERROR 2 (No such file or directory) in exec.cpp line 588 (js_execfile) opening "/sbbs/exec/jsexec.js" access=0

term Node 2 <Amr> !ERROR 2 (No such file or directory) in exec.cpp line 588 (js_execfile) opening "/sbbs/exec/jsexec.js" access=0

You have something trying to execute "?jsexec" - whether that's your custom shell or your configured chat pager, I can't know because I can't see your files. Do some searching through your config files (e.g. ctrl/*.ini) and JS files (e.g. mods/*.js) for "?jsexec" and fix that where you find it. This is something that you did/configured, not a Synchronet issue.
--
digital man (rob)

Steven Wright quote #23:
My mechanic told me, I couldn't repair your brakes, so I made your horn louder Norco, CA WX: 64.9øF, 68.0% humidity, 9 mph W wind, 0.00 inches rain/24hrs
--- Synchronet 3.21a-Linux NewsLink 1.2
* Vertrauen - Riverside County, California - telnet://vert.synchro.net
--- Synchronet 3.20b-Win32 NewsLink 1.2

From Newsgroup: alt.bbs.synchronet

To: Digital Man
Re: paging sysop
By: Digital Man to Amessyroom on Tue Apr 29 2025 11:36 am

Re: paging sysop
By: Amessyroom to All on Mon Apr 28 2025 11:37 pm

Has there been any changes to bbs.page_sysop

Paging Amessyroom...
!ERROR opening /sbbs/exec/jsexec.js
The sysop has been notified.
[Hit a key]

User reported it not working, and when trying to recreate noticed
the above error.

There is not a jsexec.js but a jsexec (executable) in /sbbs/exec.

Not sure if this is in js code for the command shell or c code.

Wondering if anybody else has encountered this. Redownloaded from git
and rebuilt tonight and the error continues.

Check what you have configured in SCFG->Chat Features->External Sysop Chat Pagers. Sounds like you've added something there incorrectly. --
digital man (rob)

Could be but even if I clear it and try and page I get the jsexec.js error which I'm not referencing
directly.

[pager:0]
cmd=?postmsg.js -i/home/sbbs/page-message.txt -terrol -nmobilenumber@att.net -fAmessyroomn "-sUser Paging You" mail
ars=
settings=0

Is what I've tried to add in chat.ini, but it seems when viewed or edited in scfg it is truncated.

Where I sent an email to my cell #. This works manually if you do jsexec postmsg.js ....

But like I said, if there is nothing defined in chat.ini or SCFG options for external pager; selecting page still gets
error in classic synchronet command shell and my customized one.

So there still seems to be something that is triggering the call to jsexec.js which doesn't exist.

So still at a loss of how to correct the issue.

error.log shows:
term Node 1 <Daniel Garrod> !ERROR 2 (No such file or directory) in exec.cpp line 588 (js_execfile) opening "/sbbs/exec/jsexec.js" access=0

term Node 2 <Amr> !ERROR 2 (No such file or directory) in exec.cpp line 588 (js_execfile) opening "/sbbs/exec/jsexec.js" access=0
---
Amessyroom
toolazy.synchro.net:2323 (telnet)
---
þ Synchronet þ Too Lazy BBS - toolazy.synchro.net:2323
--- Synchronet 3.21a-Linux NewsLink 1.2
* Vertrauen - Riverside County, California - telnet://vert.synchro.net
--- Synchronet 3.20b-Win32 NewsLink 1.2

From Newsgroup: alt.bbs.synchronet

To: Digital Man
Re: paging sysop
By: Digital Man to Amessyroom on Wed Apr 30 2025 06:48 pm

You have something trying to execute "?jsexec" - whether that's your custom shell or your configured chat pager, I can't know because I can't see your files. Do some searching through your config files (e.g. ctrl/*.ini) and JS files (e.g. mods/*.js) for "?jsexec" and fix that where you find it. This is something that you did/configured, not a Synchronet issue.

Finally figured out I had to stop and start sbbs to get the modified
chat.ini loaded; to read the cleaned value.

I was expecting logging out and back in would pick up the change, but
was wrong.

I see you have updated wiki on quoting stuff also; I'll review that.
as I don't why ?postmsg.js would cause issue -- unless it was quoting.

I have successfully setup a python script to be called by
JavaScript, so I can have username and node # in a sysop page.
---
Amessyroom
toolazy.synchro.net:2323 (telnet)
---
þ Synchronet þ Too Lazy BBS - toolazy.synchro.net:2323
--- Synchronet 3.21a-Linux NewsLink 1.2
* Vertrauen - Riverside County, California - telnet://vert.synchro.net
--- Synchronet 3.20b-Win32 NewsLink 1.2

From Newsgroup: alt.bbs.synchronet

To: Amessyroom
Re: paging sysop
By: Amessyroom to Digital Man on Fri May 02 2025 07:37 pm

Re: paging sysop
By: Digital Man to Amessyroom on Wed Apr 30 2025 06:48 pm

You have something trying to execute "?jsexec" - whether that's your custom shell or your configured chat pager, I can't know because I can't see your files. Do some searching through your config files (e.g. ctrl/*.ini) and JS files (e.g. mods/*.js) for "?jsexec" and fix that where you find it. This is something that you did/configured, not a Synchronet issue.

Finally figured out I had to stop and start sbbs to get the modified chat.ini loaded; to read the cleaned value.

You don't (normally) need to stop and restart sbbs to reload .ini files. When saving changes in SCFG, it automatically flags the sbbs instance to recycle (reload config changes and restart servers and services).

I was expecting logging out and back in would pick up the change, but
was wrong.

Only if the node has been flagged for recycle (as is done by SCFG) or a specific set of config files are hand-edited. Hand-editing chat.ini won't cause an automatic recycle.

I see you have updated wiki on quoting stuff also; I'll review that.
as I don't why ?postmsg.js would cause issue -- unless it was quoting.

Are you talking about the string literals in .ini files? I don't think that has anything to do with your reported "?jsexec" error.

I have successfully setup a python script to be called by
JavaScript, so I can have username and node # in a sysop page.

That shouldn't be necessary. You can directly execute the python script from SBBS and pass the username and node number on the command-line to the python script:
https://wiki.synchro.net/config:cmdline
--
digital man (rob)

This Is Spinal Tap quote #22:
David St. Hubbins: Here lies David St. Hubbins... and why not?
Norco, CA WX: 67.4øF, 63.0% humidity, 8 mph W wind, 0.00 inches rain/24hrs
--- Synchronet 3.21a-Linux NewsLink 1.2
* Vertrauen - Riverside County, California - telnet://vert.synchro.net
--- Synchronet 3.20b-Win32 NewsLink 1.2