Two Node system not working

21

Could you attach last page or two of a log for when you start and stop it after the error.
/var/log asterisk/messages

meanwhile I will look at your files again for contextual errors.

But my advice would be to start with a fresh set of files. Yours are fairly scrambled and it’s not easy to catch errors on view.
You only have a few areas to edit to get it running.
Make it work with one node, then add the reg string, rpt.conf entry and extensions entry for the second.
Don’t try to set it all up till you have it working with one node. then 2, then add the fluf.

22

Thanks again Mike. I’ll attach the log file.
I did get the system working with just one node that was very simple, less than an hour. Adding the second Node is not working out so well. I really didn’t do much editing I basically followed the Wiki for setting up the second node as I mentioned to Larry. I can try again but the Wiki does not seem to have all of the required changes.
var asterisk messages.pdf (18.0 KB)

23

Let me ask one question…
Did you re-use the files from your previous install ‘.conf’'s ?

24

I did not use the .conf files from the other software. I downloaded a new Beta image from the Allstar site, got a one node system running and then modified the .conf files of that single node system to be a two node system by following the Wiki and the hints I have received here.

25

Rick,

Something else you might try …
Since the Pi4 may or may not allow the configuration of 2 USB devices on Allstar.

Change one of the nodes to utilize ; rxchannel = dahdi/pseudo. and see if that helps.
Don’t forget to —> ; Enable the selected channel driver in
modules.conf !!!

Also … from looking at the log file —

[Feb 7 13:48:15] WARNING[727] config.c: parse error: No category context for line
1 of /etc/asterisk/extensions.conf

Jumping to your extensions.conf file

[globals] says or did say at one point…

HOMENPA = 910 ; change this to your Area Code
NODE = 1331 ; change this to your node number

Remove the line NODE = … if you haven’t already …it doesn’t belong.

Larry - N7FM

26

Cancel my last about removing Node =
I didn’t realize until I just now looked that they were defining a $value rather than hard coding an extension.

I will go over in the corner and hang my head now … i will add no more confusion.

Larry - N7FM

27

Well then, lets have a look at your modules.conf

28

BTW…
Looking at your files again and wondering why I never seen it the first time,
You are trying to register ‘PRIVATE NODES’

register=1335:xxxxxxxxxxx@register.allstarlink.org

If you are using only private nodes, you do not need to reg them.

I’m going to assume you wanted public connectable nodes.so get your correct node numbers or drop trying to reg them if you want only private nodes.

29

You’re right Mike I want these to be private nodes, so I have commented out those lines.
I am testing different configurations so my cycle time is getting longer and the code is blurry now.
I’ll attach my modules.conf file
modules.pdf (22.0 KB)

30

Thanks Larry,
I changed Node 2 to dahdi/pseudo instead of SimpleUSB and now I only get one error starting asterisk

[Feb 8 11:13:40] WARNING[1038] config.c: parse error: No category context for line 1 of /etc/asterisk/modules.conf
[Feb 8 11:13:40] WARNING[1038] loader.c: No ‘modules.conf’ found, no modules will be loaded.

The rpt.conf, SImpleUSB, iax, and extensions errors are gone now?

31

Oh no, don’t quit now we may be making progress. Thanks for your help

32

This modules.conf may help in cases where the beta won’t run.
https://raw.githubusercontent.com/AllStarLinkInc/ASL-Live-Build/master/config/includes.chroot/etc/asterisk.asl/modules.conf

This is the modules.conf from ASL 1.01 with one minor but critical modification:

load => res_smdi.so ; Simplified Message Desk Interface (SMDI)

I would avoid loading modules you do not need until you need them.
Stick with the basics until you have it running.
You should be able to take the one in the link and only adjust simpleusb/usbradio

33

This is what my installed modules.conf looks like on a beta vps install.
So I’m not sure where the one you posted came from.

;
; Asterisk configuration file
;
; Module Loader configuration file
;

[modules]
autoload=yes
noload => chan_pi.so
noload => chan_beagle.so
noload => func_odbc.so
noload => chan_tlb.so
noload => chan_agent.so
noload => app_voicemail.so
noload => chan_mgcp.so
noload => res_odbc.so
noload => res_snmp.so
noload => res_jabber.so
noload => app_festival.so
noload => pbx_gtkconsole.so
noload => pbx_kdeconsole.so
noload => app_intercom.so
noload => chan_modem.so
noload => chan_modem_aopen.so
noload => chan_modem_bestdata.so
noload => chan_modem_i4l.so
noload => chan_capi.so
noload => chan_skinny.so
noload => chan_vpb.so
noload => chan_alsa.so
noload => cdr_sqlite.so
noload => res_musiconhold.so
noload => app_directory_odbc.so
noload => app_voicemail_odbc.so
noload => app_voicemail_imap.so
noload => res_config_odbc.so
noload => res_config_pgsql.so
noload => app_followme.so
noload => app_queue.so ;
noload => app_cdr.so ; Tell Asterisk to not maintain a CDR for
noload => app_chanisavail.so ; Check channel availability
noload => app_channelredirect.so ; Channel Redirect
noload => app_chanspy.so ; Listen to the audio of an active channel
noload => app_controlplayback.so ; Control Playback Application
noload => app_dahdibarge.so ; Barge in on channel application
noload => app_dahdiras.so ; DAHDI RAS Application
noload => app_dahdiscan.so ; Scan Zap channels application
noload => app_db.so ; Database Access Functions
noload => app_forkcdr.so
noload => app_gps.so ; GPS interface module
noload => app_hasnewvoicemail.so ; Indicator for whether a voice mailbox ha
noload => app_ices.so ; Encode and Stream via icecast and ices
noload => app_image.so ; Image Transmission Application
noload => app_lookupblacklist.so ; Look up Caller*ID name/number from black
noload => app_lookupcidname.so ; Look up CallerID Name from local databas
noload => app_meetme.so ; MeetMe conference bridge
noload => app_milliwatt.so ; Digital Milliwatt (mu-law) Test Applicat
noload => app_mixmonitor.so ; Mixed Audio Monitoring Application
noload => app_morsecode.so ; Morse code
noload => app_mp3.so ; Silly MP3 Application
noload => app_nbscat.so ; Silly NBS Stream Application
noload => app_page.so ; Page Multiple Phones
noload => app_parkandannounce.so ; Call Parking and Announce Application
noload => app_settransfercapability.so
noload => cdr_odbc.so
noload => cdr_csv.so ; Comma Separated Values CDR Backend
noload => cdr_custom.so ; Customizable Comma Separated Values CDR
noload => cdr_manager.so ; Asterisk Manager Interface CDR Backend
noload => app_zapateller.so
noload => func_moh.so
noload => app_flash.so
noload => cdr_pgsql.so
noload => chan_gtalk.so
load => chan_usrp.so ; GNU Radio interface USRP Channel Driver

[global]

***Your modules file should not look like mine as it is for a specific different install.
Use the one in the link above or the one that comes with the install.

34

Hi Mike, I got my image from the Pi2-3-4 download at this link:
https://wiki.allstarlink.org/wiki/Beginners_Guide#ASL_Beta_Images
Maybe I should not have tried the Beta 6 release but I thought that I would need it for the Pi4
My modules.conf file cam from that image.

35

One other suggestion. Change the Channel driver for the Node 2 to dahdi/pseudo and see if that error goes away.

Something I should have asked WAY back… Do you have actual USB sound devices plugged in to the Pi when it boots?

I’m not certain as I don’t have a Pi 4 but it may be using the USB sound drivers and not having the devices available for access that, that isn’t causing the problem using the Beta software?

Larry - N7FM

36

Meant Node 1 as Node 2 you have already done

Larry

37

Start with a fresh set of files and set-up one node, copy those files for back-up and proceed to mount 2nd node.

If you look at your modules file, you will see it is from a ‘DIAL’ install. Few few versions back.
Or are you sure you installed the right software ?

38

Ok, tried that, same modules error

39

Chuck sent me his config files from a 3 node system that he is running on an Intel machine. I loaded a fresh image, his .conf files and changed all of the “load” s in the Modules files to noload except for the load => res_smdi.so.
Still get the same module errors
No context for line 1 and no modules.conf found

This is the image that I downloaded:
asl-2.0.0-beta.6-kc1kcc-20210324-rpi-armhf.img.zip

40

Latest Wiki warning…

Notices and Warnings

  • If you are restoring configuration files from another node, do NOT bring over modules.conf, as your node will not start if you do