Before I broke MBSE (see previous posting), I was having issues with getting the nodelist compiled. Kept getting /opt/mbse/var/nodelist/files.node (or node.file) not found.

I was running the mbindex utility but wasn't doing anything.

--- MultiMail/Linux v0.49
* Origin: The BABBLE BBS * babblebbs.no-ip.org * Tucson * (1:114/201)

On 2018 Mar 09 23:05:00, you wrote to All:

Before I broke MBSE (see previous posting),

you must have really broken it... the last posting i see in here from you was on 2017 Apr 16 to shawn highfield... subject line of "Re: MBSE 1.07 - trying to
compile"...

this was your path then:
@PATH: 114/201 266/512 140/1 3634/12

and this is your path now:
@PATH: 114/201 266/512 261/38 3634/12


)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... You can call me Hal, or you can call me Pal, or you...
---
* Origin: (1:3634/12.73)

you must have really broken it... the last posting i see in here
from you was on 2017 Apr 16 to shawn highfield... subject line
of "Re: MBSE 1.07 - trying to compile"...

I had posted a message before the one to which you replied about
getting a Socket error. :)

--- MultiMail/Win32 v0.50
* Origin: The BABBLE BBS * babblebbs.no-ip.org * Tucson * (1:114/201)

On 2018 Mar 12 11:06:00, you wrote to me:

you must have really broken it... the last posting i see in here
from you was on 2017 Apr 16 to shawn highfield... subject line
of "Re: MBSE 1.07 - trying to compile"...

I had posted a message before the one to which you replied about
getting a Socket error. :)

for whatever reason, it doesn't appear to have arrived here and no one else has
reported seeing it :?

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... Sign my petition to have McDonald's declared a toxic waste dump.
---
* Origin: (1:3634/12.73)

for whatever reason, it doesn't appear to have arrived here and
no one else has reported seeing it :?

Here it is again:

<snip>
I've compiled 1.0.74 on a Slackware VM and was configuring it. I did
some configuration change (not sure what or where) and I now get

socket send error 111
PANIC: cannot access socket

I can't launch "mbsetup" to see if I can fix this so I'm stuck. This
was going to be a telnet-only configuration and one of the last
configuration menus was the modems, I think.
<snip>

Thanks!


--- MultiMail/Win32 v0.50
* Origin: The BABBLE BBS * babblebbs.no-ip.org * Tucson * (1:114/201)

Hello Dane!

15 Mar 18 05:14, you wrote to Mark Lewis:

I've compiled 1.0.74 on a Slackware VM and was configuring it. I did
some configuration change (not sure what or where) and I now get

socket send error 111
PANIC: cannot access socket

I can't launch "mbsetup" to see if I can fix this so I'm stuck. This
was going to be a telnet-only configuration and one of the last configuration menus was the modems, I think.
<snip>

Thanks!

A socket send error when trying to start any of the BBS programs usually means that the mbtask daemon is not running. su to root, and run /etc/rc.d/init.d/mbsed status. If you receive a message that mbtask is not running, start it by running (as root) /etc/rc.d/init.d/mbsed start.

If mbtask is in fact already running, it sounds like you may have incorrect permissions on some/all of the BBS files.

Andrew


--- GoldED+/LNX 1.1.5-b20170303
* Origin: Phoenix BBS * phoenix.bnbbbs.net (1:320/219)

If mbtask is in fact already running, it sounds like you may
have incorrect permissions on some/all of the BBS files.

Thanks, mbtask is running. I've looked around in the various
directories but I'm not finding anything that doesn't belong to the
mbse user.

However, I finally figured it out. I was trying various binaries in
the /opt/mbse/bin directory and found that "./mbstat c" to close the
BBS closed whatever was still stuck open. I'm now able to use
"mbsetup" again.

Still trying to figure out how to poll my hub though. :)

--- MultiMail/Win32 v0.50
* Origin: The BABBLE BBS * babblebbs.no-ip.org * Tucson * (1:114/201)

Hello Dane!

15 Mar 18 19:31, you wrote to me:

Thanks, mbtask is running. I've looked around in the various
directories but I'm not finding anything that doesn't belong to the
mbse user.

However, I finally figured it out. I was trying various binaries in
the /opt/mbse/bin directory and found that "./mbstat c" to close the
BBS closed whatever was still stuck open. I'm now able to use
"mbsetup" again.

Still trying to figure out how to poll my hub though. :)

mbout poll f219.n320.z1.fidonet should do the trick, substituting the correct address for your hub of course.

Andrew

--- GoldED+/LNX 1.1.5-b20170303
* Origin: Phoenix BBS * phoenix.bnbbbs.net (1:320/219)

mbout poll f219.n320.z1.fidonet should do the trick,
substituting the correct address for your hub of course.

Still getting the echos configured as I'm entering messages in a few
but "mbout scan" isn't finding them. I've tried "mbout scan -full" as
well.

Tossing incoming mail shows

"Node 1:266/512 not connected to area BLUEWAVE"
Tossing in bad board

1:266/512 is my uplink and I've flagged the areas as having that node
as the uplink (and BACKBONE.NA) is set as the areas file.

--- MultiMail/Win32 v0.50
* Origin: The BABBLE BBS * babblebbs.no-ip.org * Tucson * (1:114/201)

On 03/09/18, Dane Beko said the following...

Before I broke MBSE (see previous posting), I was having issues with getting the nodelist compiled. Kept getting /opt/mbse/var/nodelist/files.node (or node.file) not found.

I was running the mbindex utility but wasn't doing anything.

Everything is case sensitive, so the name you give the nodelist in mbsetup
must match the name of the nodelist in /opt/mbse/var/nodelist

ie: in mbsetup you call it nodelist and the filename is NODELIST.101 it wil fail because it expects to find nodelist.101

--- Mystic BBS v1.12 A38 2018/01/01 (Raspberry Pi/32)
* Origin: internal dimension + idbbs.dlinkddns.com + port 59 (1:229/275)

ie: in mbsetup you call it nodelist and the filename is NODELIST.101 it wil fail because it expects to find nodelist.101

Thanks, this is correctly configured; what I'm seeing now is that when the mbcico utility tosses mail, everything ends up in the 'bad' echo because there's something missing in my configuration that tells MBSE that I have an uplink configured for each conference. Still working on this one. :)


--- MultiMail/Linux v0.49
* Origin: The BABBLE BBS * babblebbs.no-ip.org * Tucson * (1:114/201)

Hello Dane!

25 Mar 18 20:20, you wrote to Dave Vandermeer:

Thanks, this is correctly configured; what I'm seeing now is that when
the mbcico utility tosses mail, everything ends up in the 'bad' echo because there's something missing in my configuration that tells MBSE
that I have an uplink configured for each conference. Still working
on this one. :)

Is your uplink listed as a Connection in each area? MBSETUP 9.2.26

Andrew

--- GoldED+/LNX 1.1.5-b20170303
* Origin: Phoenix BBS * phoenix.bnbbbs.net (1:320/219)

On 03/25/18, Dane Beko said the following...

Thanks, this is correctly configured; what I'm seeing now is that when
the mbcico utility tosses mail, everything ends up in the 'bad' echo because there's something missing in my configuration that tells MBSE
that I have an uplink configured for each conference. Still working on this one. :)

Add your uplinks to the group that the conference is a part of then reselect the group to add all your links

--- Mystic BBS v1.12 A38 2018/01/01 (Raspberry Pi/32)
* Origin: internal dimension + idbbs.dlinkddns.com + port 59 (1:229/275)