Difference between revisions of "How to Move a Node from one machine to another"

From "PTTLink Wiki"
Jump to navigation Jump to search
Tag: visualeditor-switched
Tag: visualeditor-switched
Line 19: Line 19:
 
restart asterisk again
 
restart asterisk again
  
check for errors
+
check for errors in the Asterisk Console and /var/log/asterisk/messages.
 +
Logs sometimes appear in /etc/asterisk/messages
  
 
if:
 
if:
Line 30: Line 31:
 
<code>ls -la /dev/dsp</code>
 
<code>ls -la /dev/dsp</code>
  
 +
Credit belongs to N4IRS for the direct above commands.
  
if /dev/dsp is something like this: crw-rw---- 1 root audio 14, 3 May 15 18:49 /dev/dsp
+
 
 +
if:
 +
/dev/dsp is something like this:  
 +
crw-rw---- 1 root audio 14, 3 May 15 18:49 /dev/dsp
 
then:
 
then:
 
<code>chmod 775 /dev/dsp </code>
 
<code>chmod 775 /dev/dsp </code>

Revision as of 02:20, 16 May 2018

if you are not going to use first-time.sh (and it's name derivatives) or, you are moving your ASL node to an existing Debian or Ubuntu machine; or, just want to do things some arbitrary way:

Do the following:


Copy the ENTIRE /etc/asterisk folder from the WORKING ASL node machine to: - another Linux/Windows box for safe keeping, - (and replace the existing) to your new node host ASL machine


perform side-by-side comparisons to make confirm correct file copy

restart asterisk

plug in the URI

restart asterisk again

check for errors in the Asterisk Console and /var/log/asterisk/messages. Logs sometimes appear in /etc/asterisk/messages

if: you get this message: WARNING[23791]: chan_simpleusb.c:2149 setformat: Unable to re-open DSP device 2 (usb28569): No such file or directory then: echo snd_pcm_oss >>/etc/modules and either modprobe snd_pcm_oss and check for /dev/dsp or reboot. ls -la /dev/dsp

Credit belongs to N4IRS for the direct above commands.


if: /dev/dsp is something like this: crw-rw---- 1 root audio 14, 3 May 15 18:49 /dev/dsp then: chmod 775 /dev/dsp

systemctl status check to see if any process have failed usually restarting Asterisk will cause the update node list service to fail. In this case, you may see something such as: State: degraded

    Jobs: 0 queued
  Failed: 1 units

systemctl --failed

UNIT                   LOAD   ACTIVE SUB    DESCRIPTION

● updatenodelist.service loaded failed failed AllStar NodeList updater


systemctl restart updatenodelist.service

if that does not work, then: service updatenodelist restart