Hey guys,

I'm getting an error from two of my timed events, FidoIn and FidoOut.

It's returning the following (in RED), and it is listed in my error log.

It says "1/14 10:42:47p Timed event: FIDOIN returned 1"

And the same for FidoOut. WHat does 'Returned 1' mean?

It looks like it stopped importing messages.

Also, what are you guys using for TIC processing? I've been setting up Tic_hog, but I cannot get it to write to the message bases.

Thanks...




--
Eric Hutchins, K7ELH
Sysop
Eye of the Storm BBS
bbs.k6sdg.org

---
� Synchronet � Eye of the Storm - bbs.k6sdg.org

Re: error...
By: K7ELH to All on Sat Jan 14 2017 23:37:45

Can't answer the error question but I use TinyTic to process inbound files and AllFix top handle outbound,

---
� Synchronet � Split Infinity BBS - Rupert, WV

Hello K7ELH,

On Sat Jan 14 2017 23:37:44, K7ELH wrote to All:

I'm getting an error from two of my timed events, FidoIn and FidoOut.

It's returning the following (in RED), and it is listed in my error
log.

It says "1/14 10:42:47p Timed event: FIDOIN returned 1"

And the same for FidoOut. WHat does 'Returned 1' mean?

I believe it means they failed to complete their run. Try running it directly from the command line and see what error it reports (ie: sbbsecho -les .. or whatever you run in your original timed event).

It looks like it stopped importing messages.

That will be the case unless both of those events return 0.

Also, what are you guys using for TIC processing? I've been setting up Tic_hog, but I cannot get it to write to the message bases.

Nothing will externally write to your Synchronet message bases except for smbutil. So if this tic processor you're using can output it's results to a text file, you can use smbutil to import that text file into a message base.

Regards,
Nick

... "Не знаю. Я здесь только работаю."
--- GoldED+/LNX 1.1.5-b20161221
* Origin: thePharcyde_ distribution system (Wisconsin) (723:1/1)
� Synchronet � thePharcyde_

Re: RE: error...
By: Buckaroo Banzai to K7ELH on Sun Jan 15 2017 07:49 am

Thanks.. I'll check TinyTic out when I get this other issue fixed.
Eric, K7ELH

---
� Synchronet � realitycheckBBS -- http://realitycheckBBS.org

Re: error...
By: Accession to K7ELH on Sun Jan 15 2017 09:19 am

I'm getting an error from two of my timed events, FidoIn and FidoOut.
It's returning the following (in RED), and it is listed in my error
log.
It says "1/14 10:42:47p Timed event: FIDOIN returned 1"

I believe it means they failed to complete their run. Try running it directly from the command line and see what error it reports (ie: sbbsecho -les .. or whatever you run in your original timed event).

Thanks, I'll check that out. Seems like it stopped as soon as I upgraded to 3.17.

Tic_hog, but I cannot get it to write to the message bases.

Nothing will externally write to your Synchronet message bases except for smbutil. So if this tic processor you're using can output it's results to a text file, you can use smbutil to import that text file into a message base.

Yeah, Tic_hog runs a batch file the calls SMBUTIL, but maybe it's written for an older version and the noptions are incorrect.

Wish me luck!

Eric, K7ELH

---
� Synchronet � realitycheckBBS -- http://realitycheckBBS.org

Hello K7elh,

On Sun Jan 15 2017 18:13:58, K7elh wrote to Accession:

I believe it means they failed to complete their run. Try running
it directly from the command line and see what error it reports
(ie: sbbsecho -les .. or whatever you run in your original timed
event).

Thanks, I'll check that out. Seems like it stopped as soon as I
upgraded to 3.17.

Did you run the javascript upgrade file that converts your sbbsecho.cfg to sbbsecho.ini?

Tic_hog, but I cannot get it to write to the message bases.

Nothing will externally write to your Synchronet message bases
except for smbutil. So if this tic processor you're using can
output it's results to a text file, you can use smbutil to import
that text file into a message base.

Yeah, Tic_hog runs a batch file the calls SMBUTIL, but maybe it's
written for an older version and the noptions are incorrect.

All these years, and I've never heard of Tic_hog. Or ever knew that anything actually called smbutil by default.

Regards,
Nick

... "Не знаю. Я здесь только работаю."
--- GoldED+/LNX 1.1.5-b20161221
* Origin: thePharcyde_ distribution system (Wisconsin) (723:1/1)
� Synchronet � thePharcyde_ te

Re: error...
By: Accession to K7elh on Sun Jan 15 2017 09:57 pm

Did you run the javascript upgrade file that converts your sbbsecho.cfg to sbbsecho.ini?

Umm.. A javascript upgrade file? I saw no such thing when I upgraded. All I did wa copy the the files over my ol;d one (after I backed them up of course). I am going to restore the backup until I get this figured out.

All these years, and I've never heard of Tic_hog. Or ever knew that anything actually called smbutil by default.
Nick

Yeah, it's a small utility that I found that says it is specifically for Synchronet. If you would like to look at it, I have it, and I can netmail it to you.

Eric, K7ELH
---
� Synchronet � Vertrauen � Home of Synchronet � telnet:/

Hello K7elh,

On Mon Jan 16 2017 20:47:54, K7elh wrote to Accession:

sbbsecho.cfg to sbbsecho.ini?

Umm.. A javascript upgrade file? I saw no such thing when I upgraded.
All I did wa copy the the files over my ol;d one (after I backed them
up of course). I am going to restore the backup until I get this
figured out.

Not sure if you're running Windows or Linux, but there's a reference about it here:

http://wiki.synchro.net/install:win?s[]=sbbsecho&s[]=upgrade

Once you upgrade, just do this:

"Download the sbbsecho_upgrade.js file and copy to the exec directory. Open a command prompt and navigate to the exec directory. Run the upgrade script using
the following command: jsexec sbbsecho_upgrade.js"

That will convert your sbbsecho.cfg to the newly used sbbsecho.ini for you, and
it should work as expected afterwards. This is the new format for sbbsecho v3.x..

All these years, and I've never heard of Tic_hog. Or ever knew that
anything actually called smbutil by default.

Yeah, it's a small utility that I found that says it is specifically
for Synchronet. If you would like to look at it, I have it, and I can netmail it to you.

Question is, when was it last updated? Is it new, or fairly old? It may not work with later versions of Synchronet.

Regards,
Nick

... "Не знаю. Я здесь только работаю."
--- GoldED+/LNX 1.1.5-b20161221
* Origin: thePharcyde_ distribution system (Wisconsin) (723:1/1)

Re: error...
By: K7ELH to All on Sat Jan 14 2017 11:37 pm

Hey guys,

I'm getting an error from two of my timed events, FidoIn and FidoOut.

It's returning the following (in RED), and it is listed in my error log.

It says "1/14 10:42:47p Timed event: FIDOIN returned 1"

And the same for FidoOut. WHat does 'Returned 1' mean?

It means the process/program started for the "FIDOIN" event returned a non-zero error level to the calling process (the BBS). Your data/sbbsecho.log file should have the details of the reason for the error.

It looks like it stopped importing messages.

Yes, they're likely related.

digital man

Synchronet "Real Fact" #19:
The first Synchronet BBS (Vertrauen) went live in July of 1991 (replacing WWIV).
Norco, CA WX: 53.8�F, 78.0% humidity, 7 mph E wind, 0.00 inches rain/24hrs
---
� Synchronet � Vertrauen � Home of Synchronet � telnet://vert.synchro.net

Re: error...
By: K7elh to Accession on Mon Jan 16 2017 08:47 pm

Re: error...
By: Accession to K7elh on Sun Jan 15 2017 09:57 pm

Did you run the javascript upgrade file that converts your sbbsecho.cfg to sbbsecho.ini?

Umm.. A javascript upgrade file? I saw no such thing when I upgraded. All I did wa copy the the files over my ol;d one (after I backed them up of course). I am going to restore the backup until I get this figured out.

When upgrading from SBBSecho v2 to SBBSecho v3, you need to run "jexec sbbsecho_upgrade.js" (just one time). This will create the necessary ctrl/sbbsecho.ini file.

digital man

Synchronet/BBS Terminology Definition #19:
DTE = Data Terminal Equipment
Norco, CA WX: 53.8�F, 78.0% humidity, 7 mph E wind, 0.00 inches rain/24hrs
---
� Synchronet � Vertrauen � Home of Synchronet � telnet://vert.synchro.net

When upgrading from SBBSecho v2 to SBBSecho v3, you need to run "jexec sbbsecho_upgrade.js" (just one time). This will create the necessary ctrl/sbbsecho.ini file.

digital man

Okay, I've got it. The odd thing was that I am not upgrading from v2 to v3. I was upgrading from v3.16 to 3.17.

Was the *.cfg to *.ini conversion take place in between these to versions? I guess it doesn't matter as long as it works...

I guess I'll need to learn a little more about Javascript. I know next to nothing about it now.

--
Eric Hutchins, K7ELH
Sysop
Eye of the Storm BBS
bbs.k6sdg.org

---
� Synchronet � Eye of the Storm - bbs.k6sdg.org

On 01/18/17, K7ELH said the following...

When upgrading from SBBSecho v2 to SBBSecho v3, you need to run "jexec sbbsecho_upgrade.js" (just one time). This will create the necessary ctrl/sbbsecho.ini file.

Okay, I've got it. The odd thing was that I am not upgrading from v2 to v3. I was upgrading from v3.16 to 3.17.

v2 of SBBSecho is what is used in v3.16 of Synchronet. When you upgrade to v3.17, it also needs to upgrade SBBSecho to v3.

Hope this clears things up a bit.


Dan Richter
aka Black Panther
Sysop - Castle Rock BBS

--- Mystic BBS v1.12 A31 (Windows)
* Origin: Castle Rock BBS - castlero.duckdns.org

Re: Re: error...
By: K7ELH to Digital Man on Wed Jan 18 2017 22:41:40

Okay, I've got it. The odd thing was that I am not upgrading from v2 to v3. I was upgrading from v3.16 to 3.17.

The upgrade in question here is of sbbsecho rather than Synchronet as a whole. The v2/v3 applies to that utility.

I guess I'll need to learn a little more about Javascript. I know next to nothing about it now.

You don't really need to, but knowing a bit can help you tweak your BBS.

The main thing to know here is that the 'jsexec' utility can be used to run a Synchronet javascript file from a shell/command prompt. You'll occasionally need to use it to execute scripts like this that perform housekeeping tasks. No actual knowledge of JS is required in order to do that.

---
echicken
electronic chicken bbs - bbs.electronicchicken.com - 416-273-7230
� Synchronet � electronic chicken bbs - bbs.electronicchicken.com

Re: Re: error...
By: K7ELH to Digital Man on Wed Jan 18 2017 10:41 pm

When upgrading from SBBSecho v2 to SBBSecho v3, you need to run "jexec sbbsecho_upgrade.js" (just one time). This will create the necessary ctrl/sbbsecho.ini file.

Okay, I've got it. The odd thing was that I am not upgrading from v2 to v3. I was upgrading from v3.16 to 3.17.

SBBecho v2.x was included with Synchronet v3.16. The current development version of SBBSecho is v3.0. You could run SBBSecho v3 with Synchronet v3.16 or SBBSecho v2 with Synchronet v3.17, that's why they have different version numbers.

digital man

Synchronet/BBS Terminology Definition #25:
FTS = FidoNet Technical Standard
Norco, CA WX: 56.2�F, 80.0% humidity, 7 mph E wind, 0.62 inches rain/24hrs
---
� Synchronet � Vertrauen � Home of Synchronet � telnet://vert.synchro.net

On 01/18/17, K7ELH said the following...

Okay, I've got it. The odd thing was that I am not upgrading from v2 to v3. I was upgrading from v3.16 to 3.17.

v2 of SBBSecho is what is used in v3.16 of Synchronet. When you upgrade to v3.17, it also needs to upgrade SBBSecho to v3.

Hope this clears things up a bit.

Got it... Thanks Dan
--
Eric Hutchins, K7ELH
Sysop
Eye of the Storm BBS
bbs.k6sdg.org

---
� Synchronet � Eye of the Storm - bbs.k6sdg.org