Date   

Re: Asterisk Error

K4VL
 

Yes it is a Raspberry Pi. I ran that and it returned this.
fsck.ext4: No such file or directory while trying to open /dev/sd**
Possibly non-existent device?

I think I will go out today and buy a new SDCard. It won't take log to reconfigure it. I have all the necessary files backed up. Thanks to your help in the past I can get it up and going pretty quick. Now that I have said that I will be on here after work asking more questions.
I am wondering if any of you know how I can make WinSCP allow me to write to my files. I found a command sudo su -c /bin/sftp-server I put in the SFTP Protocols and it worked for a while but now tells me Cannot initialize SFTP protocol. Is the host running an SFTP server? when I try to use it.

Thanks

Virus-free. www.avg.com


On Wed, Mar 27, 2019 at 7:01 AM Steve KC1AWV <smiller@...> wrote:
Is this a Raspberry Pi? Maybe the SD card is going bad, corrupting the filesystem and forcing it to be read-only. You can force a fsck by running

fsck.ext4 -cDfty -C 0 /dev/sd**

You can also run dmesg which may give a clue into why the filesystem is read only.

It sounds like asterisk won't start because it can't write its log file, which may be the underlying issue here.

On Wed, Mar 27, 2019 at 7:49 AM K4VL <73dek4vl@...> wrote:
OK this might help. It say it can't write the log files because it is a read only system. After a Google search I found how to remount. I still get the error when I status asterisk. I reran
journalctl -u asterisk.service --since today and got the log I have attached. When I try running asterisk -vcd I get an error stating again that the log file can't be written because it is a read only system.


Virus-free. www.avg.com

On Wed, Mar 27, 2019 at 4:34 AM Steve N4IRS <szingman@...> wrote:
I would at least run asterisk in the foreground with:
asterisk -vcd

On 3/27/19 5:33 AM, Steve KC1AWV wrote:
If the logs are empty, then it's going to be next to impossible to diagnose the problem. Log files are the single most important thing on a computer, and without them, you're flying blind.

At this point, I'd say back up the configuration files and put them somewhere for reference and start over.

On Tue, Mar 26, 2019, 10:25 PM K4VL <73dek4vl@...> wrote:
The logs appear empty. I event went into the asterisk log folder and opened the event log and it was blank.


Virus-free. www.avg.com



--
Steve Miller
KC1AWV


Re: Asterisk Error

Steve KC1AWV
 

Is this a Raspberry Pi? Maybe the SD card is going bad, corrupting the filesystem and forcing it to be read-only. You can force a fsck by running

fsck.ext4 -cDfty -C 0 /dev/sd**

You can also run dmesg which may give a clue into why the filesystem is read only.

It sounds like asterisk won't start because it can't write its log file, which may be the underlying issue here.


On Wed, Mar 27, 2019 at 7:49 AM K4VL <73dek4vl@...> wrote:
OK this might help. It say it can't write the log files because it is a read only system. After a Google search I found how to remount. I still get the error when I status asterisk. I reran
journalctl -u asterisk.service --since today and got the log I have attached. When I try running asterisk -vcd I get an error stating again that the log file can't be written because it is a read only system.


Virus-free. www.avg.com

On Wed, Mar 27, 2019 at 4:34 AM Steve N4IRS <szingman@...> wrote:
I would at least run asterisk in the foreground with:
asterisk -vcd

On 3/27/19 5:33 AM, Steve KC1AWV wrote:
If the logs are empty, then it's going to be next to impossible to diagnose the problem. Log files are the single most important thing on a computer, and without them, you're flying blind.

At this point, I'd say back up the configuration files and put them somewhere for reference and start over.

On Tue, Mar 26, 2019, 10:25 PM K4VL <73dek4vl@...> wrote:
The logs appear empty. I event went into the asterisk log folder and opened the event log and it was blank.


Virus-free. www.avg.com



--
Steve Miller
KC1AWV


Re: Asterisk Error

K4VL
 

OK this might help. It say it can't write the log files because it is a read only system. After a Google search I found how to remount. I still get the error when I status asterisk. I reran
journalctl -u asterisk.service --since today and got the log I have attached. When I try running asterisk -vcd I get an error stating again that the log file can't be written because it is a read only system.


Virus-free. www.avg.com

On Wed, Mar 27, 2019 at 4:34 AM Steve N4IRS <szingman@...> wrote:
I would at least run asterisk in the foreground with:
asterisk -vcd

On 3/27/19 5:33 AM, Steve KC1AWV wrote:
If the logs are empty, then it's going to be next to impossible to diagnose the problem. Log files are the single most important thing on a computer, and without them, you're flying blind.

At this point, I'd say back up the configuration files and put them somewhere for reference and start over.

On Tue, Mar 26, 2019, 10:25 PM K4VL <73dek4vl@...> wrote:
The logs appear empty. I event went into the asterisk log folder and opened the event log and it was blank.


Virus-free. www.avg.com


Re: Asterisk Error

Steve N4IRS
 

I would at least run asterisk in the foreground with:
asterisk -vcd

On 3/27/19 5:33 AM, Steve KC1AWV wrote:
If the logs are empty, then it's going to be next to impossible to diagnose the problem. Log files are the single most important thing on a computer, and without them, you're flying blind.

At this point, I'd say back up the configuration files and put them somewhere for reference and start over.

On Tue, Mar 26, 2019, 10:25 PM K4VL <73dek4vl@...> wrote:
The logs appear empty. I event went into the asterisk log folder and opened the event log and it was blank.


Re: Asterisk Error

Steve KC1AWV
 

If the logs are empty, then it's going to be next to impossible to diagnose the problem. Log files are the single most important thing on a computer, and without them, you're flying blind.

At this point, I'd say back up the configuration files and put them somewhere for reference and start over.

On Tue, Mar 26, 2019, 10:25 PM K4VL <73dek4vl@...> wrote:
The logs appear empty. I event went into the asterisk log folder and opened the event log and it was blank.


Re: Asterisk Error

Steve N4IRS
 

/var/log/asterisk/messages is empty?

On 3/26/19 10:25 PM, K4VL wrote:
The logs appear empty. I event went into the asterisk log folder and opened the event log and it was blank.


Re: Asterisk Error

K4VL
 

BTW I'm getting the same error when I look at the status of mmdvm_bridge. analog_bridge is running.


Re: Asterisk Error

K4VL
 

The logs appear empty. I event went into the asterisk log folder and opened the event log and it was blank.


Re: Asterisk Error

Steve KC1AWV
 

Ok, sorry I was thinking along the systemd lines. Run this instead

tail -n50 /var/log/asterisk/messages

That will show the actual error. The journal logs are just showing the restarts that systemd is doing 

On Tue, Mar 26, 2019, 9:06 PM K4VL <73dek4vl@...> wrote:
On Tue, Mar 26, 2019 at 12:23 PM, Steve KC1AWV wrote:
journalctl -u asterisk.service --since today
 
This is what it does every ten minutes it seams. I have no idea what this means.

-- Logs begin at Mon 2019-03-25 09:17:01 CDT, end at Tue 2019-03-26 20:04:48 CDT. --
Mar 26 17:46:39 repeater systemd[1]: asterisk.service: Service hold-off time over, scheduling restart.
Mar 26 17:46:39 repeater systemd[1]: Stopped Asterisk PBX and telephony daemon.
Mar 26 17:46:39 repeater systemd[1]: Started Asterisk PBX and telephony daemon.
Mar 26 17:46:39 repeater systemd[1]: asterisk.service: Main process exited, code=exited, status=1/FAILURE
Mar 26 17:46:39 repeater systemd[1]: asterisk.service: Control process exited, code=exited status=1
Mar 26 17:46:39 repeater systemd[1]: asterisk.service: Unit entered failed state.
Mar 26 17:46:39 repeater systemd[1]: asterisk.service: Failed with result 'exit-code'.
Mar 26 17:46:49 repeater systemd[1]: asterisk.service: Service hold-off time over, scheduling restart.
Mar 26 17:46:49 repeater systemd[1]: Stopped Asterisk PBX and telephony daemon.
Mar 26 17:46:49 repeater systemd[1]: Started Asterisk PBX and telephony daemon.
Mar 26 17:46:49 repeater systemd[1]: asterisk.service: Main process exited, code=exited, status=1/FAILURE
Mar 26 17:46:49 repeater systemd[1]: asterisk.service: Control process exited, code=exited status=1
Mar 26 17:46:49 repeater systemd[1]: asterisk.service: Unit entered failed state.
Mar 26 17:46:49 repeater systemd[1]: asterisk.service: Failed with result 'exit-code'.
Mar 26 17:46:59 repeater systemd[1]: asterisk.service: Service hold-off time over, scheduling restart.
Mar 26 17:46:59 repeater systemd[1]: Stopped Asterisk PBX and telephony daemon.
Mar 26 17:46:59 repeater systemd[1]: Started Asterisk PBX and telephony daemon.
Mar 26 17:46:59 repeater systemd[1]: asterisk.service: Main process exited, code=exited, status=1/FAILURE
Mar 26 17:46:59 repeater systemd[1]: asterisk.service: Control process exited, code=exited status=1
Mar 26 17:46:59 repeater systemd[1]: asterisk.service: Unit entered failed state.
Mar 26 17:46:59 repeater systemd[1]: asterisk.service: Failed with result 'exit-code'.
Mar 26 17:47:10 repeater systemd[1]: asterisk.service: Service hold-off time over, scheduling restart.
Mar 26 17:47:10 repeater systemd[1]: Stopped Asterisk PBX and telephony daemon.
Mar 26 17:47:10 repeater systemd[1]: Started Asterisk PBX and telephony daemon.
Mar 26 17:47:10 repeater systemd[1]: asterisk.service: Main process exited, code=exited, status=1/FAILURE
Mar 26 17:47:10 repeater systemd[1]: asterisk.service: Control process exited, code=exited status=1
Mar 26 17:47:10 repeater systemd[1]: asterisk.service: Unit entered failed state.
Mar 26 17:47:10 repeater systemd[1]: asterisk.service: Failed with result 'exit-code'.
Mar 26 17:47:20 repeater systemd[1]: asterisk.service: Service hold-off time over, scheduling restart.
Mar 26 17:47:20 repeater systemd[1]: Stopped Asterisk PBX and telephony daemon.
Mar 26 17:47:20 repeater systemd[1]: Started Asterisk PBX and telephony daemon.
Mar 26 17:47:20 repeater systemd[1]: asterisk.service: Main process exited, code=exited, status=1/FAILURE
Mar 26 17:47:20 repeater systemd[1]: asterisk.service: Control process exited, code=exited status=1


Re: Asterisk Error

K4VL
 

On Tue, Mar 26, 2019 at 12:23 PM, Steve KC1AWV wrote:
journalctl -u asterisk.service --since today
 
This is what it does every ten minutes it seams. I have no idea what this means.

-- Logs begin at Mon 2019-03-25 09:17:01 CDT, end at Tue 2019-03-26 20:04:48 CDT. --
Mar 26 17:46:39 repeater systemd[1]: asterisk.service: Service hold-off time over, scheduling restart.
Mar 26 17:46:39 repeater systemd[1]: Stopped Asterisk PBX and telephony daemon.
Mar 26 17:46:39 repeater systemd[1]: Started Asterisk PBX and telephony daemon.
Mar 26 17:46:39 repeater systemd[1]: asterisk.service: Main process exited, code=exited, status=1/FAILURE
Mar 26 17:46:39 repeater systemd[1]: asterisk.service: Control process exited, code=exited status=1
Mar 26 17:46:39 repeater systemd[1]: asterisk.service: Unit entered failed state.
Mar 26 17:46:39 repeater systemd[1]: asterisk.service: Failed with result 'exit-code'.
Mar 26 17:46:49 repeater systemd[1]: asterisk.service: Service hold-off time over, scheduling restart.
Mar 26 17:46:49 repeater systemd[1]: Stopped Asterisk PBX and telephony daemon.
Mar 26 17:46:49 repeater systemd[1]: Started Asterisk PBX and telephony daemon.
Mar 26 17:46:49 repeater systemd[1]: asterisk.service: Main process exited, code=exited, status=1/FAILURE
Mar 26 17:46:49 repeater systemd[1]: asterisk.service: Control process exited, code=exited status=1
Mar 26 17:46:49 repeater systemd[1]: asterisk.service: Unit entered failed state.
Mar 26 17:46:49 repeater systemd[1]: asterisk.service: Failed with result 'exit-code'.
Mar 26 17:46:59 repeater systemd[1]: asterisk.service: Service hold-off time over, scheduling restart.
Mar 26 17:46:59 repeater systemd[1]: Stopped Asterisk PBX and telephony daemon.
Mar 26 17:46:59 repeater systemd[1]: Started Asterisk PBX and telephony daemon.
Mar 26 17:46:59 repeater systemd[1]: asterisk.service: Main process exited, code=exited, status=1/FAILURE
Mar 26 17:46:59 repeater systemd[1]: asterisk.service: Control process exited, code=exited status=1
Mar 26 17:46:59 repeater systemd[1]: asterisk.service: Unit entered failed state.
Mar 26 17:46:59 repeater systemd[1]: asterisk.service: Failed with result 'exit-code'.
Mar 26 17:47:10 repeater systemd[1]: asterisk.service: Service hold-off time over, scheduling restart.
Mar 26 17:47:10 repeater systemd[1]: Stopped Asterisk PBX and telephony daemon.
Mar 26 17:47:10 repeater systemd[1]: Started Asterisk PBX and telephony daemon.
Mar 26 17:47:10 repeater systemd[1]: asterisk.service: Main process exited, code=exited, status=1/FAILURE
Mar 26 17:47:10 repeater systemd[1]: asterisk.service: Control process exited, code=exited status=1
Mar 26 17:47:10 repeater systemd[1]: asterisk.service: Unit entered failed state.
Mar 26 17:47:10 repeater systemd[1]: asterisk.service: Failed with result 'exit-code'.
Mar 26 17:47:20 repeater systemd[1]: asterisk.service: Service hold-off time over, scheduling restart.
Mar 26 17:47:20 repeater systemd[1]: Stopped Asterisk PBX and telephony daemon.
Mar 26 17:47:20 repeater systemd[1]: Started Asterisk PBX and telephony daemon.
Mar 26 17:47:20 repeater systemd[1]: asterisk.service: Main process exited, code=exited, status=1/FAILURE
Mar 26 17:47:20 repeater systemd[1]: asterisk.service: Control process exited, code=exited status=1


Re: Asterisk Error

Steve KC1AWV
 

Try running the command

journalctl -u asterisk.service --since today

to view more of the asterisk logs to find the error.

On Tue, Mar 26, 2019 at 1:22 PM K4VL <73dek4vl@...> wrote:
After a power failure my asterisk quit working. See the attached. I ran systemctl status asterisk



--
Steve Miller
KC1AWV


Asterisk Error

K4VL
 

After a power failure my asterisk quit working. See the attached. I ran systemctl status asterisk


Re: DMR to DSTAR

David
 

HI Steve
does dvswitch support DVmege 3003 transcode ?
http://www.dvmega.co.uk/AMBE3003%20DV%20USB%20Stick.html 

because i had this .and it can not detect this dongle


Re: DTMF

Rob WX1N
 

Thanks Steve. Any plans to add that in the future or a way, or is it too much effort to be worth it?

-----Original Message-----
From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> On Behalf Of Steve N4IRS
Sent: Sunday, March 24, 2019 15:01
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] DTMF

Rob,
The USRP_channel driver does not decode DTMF. So the answer is no, you can not decode the DTMF and control the ASL node.

73, Steve N4IRS

On 3/24/19 12:36 PM, Rob WX1N wrote:
Hi Steve and all,

Did any of you go any further with this? I have a DMR<>analog bridge going, but the USRP channel driver does not appear to decode DTMF. I've verified that the DMR radio in question does indeed transmit DTMF via the DMR audio, and that it decodes nicely in other applications, but monitoring the asterisk cli, no digits are detected. Not sure if this is a hard and fast limitation of the USRP driver, or if there is a way to configure it to pass the dtmf through to the ASL software.

Rob, WX1N



Re: DTMF

Steve N4IRS
 

Rob,
The USRP_channel driver does not decode DTMF. So the answer is no, you can not decode the DTMF and control the ASL node.

73, Steve N4IRS

On 3/24/19 12:36 PM, Rob WX1N wrote:
Hi Steve and all,

Did any of you go any further with this? I have a DMR<>analog bridge going, but the USRP channel driver does not appear to decode DTMF. I've verified that the DMR radio in question does indeed transmit DTMF via the DMR audio, and that it decodes nicely in other applications, but monitoring the asterisk cli, no digits are detected. Not sure if this is a hard and fast limitation of the USRP driver, or if there is a way to configure it to pass the dtmf through to the ASL software.

Rob, WX1N


Re: DTMF

Rob WX1N
 

Hi Steve and all,

Did any of you go any further with this? I have a DMR<>analog bridge going, but the USRP channel driver does not appear to decode DTMF. I've verified that the DMR radio in question does indeed transmit DTMF via the DMR audio, and that it decodes nicely in other applications, but monitoring the asterisk cli, no digits are detected. Not sure if this is a hard and fast limitation of the USRP driver, or if there is a way to configure it to pass the dtmf through to the ASL software.

Rob, WX1N


Re: Setting up a YSFn <--> ASL bridge

steve@...
 

Thanks for you replies!  I'm happy to say it's working now.  I plugged in the IP address instead of the name, changed the local address to 0 and the gateway port to 42001 (I tried 42000 but according to the trusty pi-star YSFHosts.txt file it said it was 42001 for Americalink).  Now I'm getting audio and it seems to be working fine.  Thanks very much for your help.
73,
Steve - W7RD


Re: Linking P25 to P25 using two mmdvm's

Mike AE4ML
 

I have done this on raspberry pi 2 and 3B+


Re: Linking P25 to P25 using two mmdvm's

Tony Steele
 

Ok,
Ignore the last, I tried a different image for the OrangePi Zero, this time I used Armbian and the install of p25reflector seems to have gone fine with no errors.

Now to proceed with the rest of the install.


Re: Which base image to use with DV Switch: Allstar or HamVoIP

David McGough
 

Hi,

Yes, I've got a alpha pre-release test package now. This weekend I'm
verifying that nothing is "badly broken." I expect a preliminary release
announcement this weekend.

73, David KB4FXC

On Sat, 23 Mar 2019, Igor Videc wrote:

David,

have you made any progress with this ?

73
Igor 9A6NVI



5961 - 5980 of 9595