Date   

Re: Help install DVSwitch in server Debian 8 64 bits for error.

Steve KC1AWV
 

For explanation of exit status 8 - that's an exec format error according to errno. Could be the package you're installing is for the wrong architecture, such as trying to install a package for ARM on an x86.


Re: Help install DVSwitch in server Debian 8 64 bits for error.

Steve KC1AWV
 

Need more info. how are you installing DVSwitch? Are you using the DVSwitch-System-Builder script?

Only references to dvswitch-base I can find is in ASL, not DVSwitch.


Help install DVSwitch in server Debian 8 64 bits for error.

EA5GVK Joaquin
 

Help. It report it error when install dvswitch:
Selecting previously unselected package dvswitch-base.
(Reading database ... 42595 files and directories currently installed.)
Preparing to unpack dvswitch-base_1.01-20180420-11_all.deb ...
Unpacking dvswitch-base (1.01-20180420-11) ...
Setting up dvswitch-base (1.01-20180420-11) ...
dpkg: error processing package dvswitch-base (--install):
 subprocess installed post-installation script returned error exit status 8
Errors were encountered while processing:
 dvswitch-base


Quick deploy DVSwitch test box

Steve KC1AWV
 

Hi everyone,

Since I do work testing and developing systems at work, I use vagrant a lot. It helps me build test virtual machines and provision them quickly to test out things. Sometimes, I need to destroy and re-provision those virtual machines in a rapid fashion, so vagrant is the way to go. If you're interested, I've put the vagrantfile and provisioning steps up on github for those interested.

https://github.com/kc1awv/dvswitch-sandbox

You'll need vagrant and virtualbox installed on a machine. Simply git clone the repo, go into the directory and run vagrant up. The system will download a bento Debian 9.6 box and install the DVSwitch programs from the DVSwitch-System-Builder script from Steve N4IRS. I also included a DMRGateway unit file for systemd in there as well.

Do not use this system in production! This is designed as a development box, so play with the configs as you see fit, then copy your configs from the vagrant box to your production system.

Questions and comments are welcomed, and I will do my best to respond as work permits.

Steve KC1AWV


Re: Linking P25 to P25 using two mmdvm's

David
 

Hi for DMR to P25 via DVswitch you can reference this blog 
http://blog.927.org/node/1


Re: Linking P25 to P25 using two mmdvm's

Tony Steele
 

Hi

Just to update the group, I managed to get this working perfectly using a MMDVM duplex hotspot (UHF) with a Orange Pi zero and a MMDVM modem pcb attached to a GM360 VHF and Raspberry Pi 2.
I also installed P25 Reflector on a seperate Raspberry Pi 2.
Following the instructions Mike gave above, aside from the issue I had with Raspbian on the Orange Pi Zero (above), everything went fine when I switched to Armbian.
It works very very well, I still have some playing to do, but very impressed so far, the total delay is just under 2 seconds and that includes the internet trip to my house.

A final question Mike if I may, how simple would it be to add in another unit with a seperate Pi and MMDVM hotspot but running DMR? I know this is now getting more complicated, but just thinking ahead a bit, would I need to install something on the third Pi currently running P25reflector to link the DMR to the P25 or is this not possible?

Thank you for all the help, it is very much appreciated.

Regards
Tony.


Re: 1 Way Audio (XLX DMR to ASL)

Steve KC1AWV
 

Thanks, I got one here I run. I'll test and let you know what I find!

On Thu, Mar 28, 2019 at 8:18 AM Daniel L. Srebnick <dan@...> wrote:
Here's hoping you are able to figure it out! If you need an XLX to test with, feel free to use XLX020 E.

73,

Dan

On Thu, 2019-03-28 at 07:43 -0400, Steve KC1AWV wrote:
Ok, unless someone else can provide clues as to what might be happening I may have to lab this and go through the steps again to recreate and solve. I plan on restructuring the system I run here this weekend anyway, so it may be a good chance to write this stuff down for future reference.

On Wed, Mar 27, 2019 at 9:58 PM Daniel L. Srebnick <dan@...> wrote:
Steve:

I changed the repeater id in Analog_Bridge.ini to 1234567 as you suggested. After restarting all the involved processes, my test results were unchanged.

On Wed, 2019-03-27 at 20:48 -0400, Steve KC1AWV wrote:
Daniel,

I've had the same issue myself before. I'm trying to remember exactly what I did to rectify the problem, but it's been a while since the last time I played with the configurations here. One thing that I do want to note is to make sure that you send only a max of a 7 digit DMR ID when going to XLX, your repeater ID has 9 digits. Try setting the repeater ID to something like 1234567 (if you don't have a second DMR ID) and test again. I'm not sure if using that ID is copacetic with every network, but it shouldn't be a problem with XLX since I think it only uses the repeater ID to lookup and display the callsign of the network you're coming in on. Your mileage may vary, caveat emptor, don't forget to turn the lights off before you leave, etc.

I would be very interested in how the test runs with that change.

Steve KC1AWV






--
Steve Miller
KC1AWV


Re: 1 Way Audio (XLX DMR to ASL)

Dan K2IE
 

Here's hoping you are able to figure it out! If you need an XLX to test with, feel free to use XLX020 E.

73,

Dan

On Thu, 2019-03-28 at 07:43 -0400, Steve KC1AWV wrote:
Ok, unless someone else can provide clues as to what might be happening I may have to lab this and go through the steps again to recreate and solve. I plan on restructuring the system I run here this weekend anyway, so it may be a good chance to write this stuff down for future reference.

On Wed, Mar 27, 2019 at 9:58 PM Daniel L. Srebnick <dan@...> wrote:
Steve:

I changed the repeater id in Analog_Bridge.ini to 1234567 as you suggested. After restarting all the involved processes, my test results were unchanged.

On Wed, 2019-03-27 at 20:48 -0400, Steve KC1AWV wrote:
Daniel,

I've had the same issue myself before. I'm trying to remember exactly what I did to rectify the problem, but it's been a while since the last time I played with the configurations here. One thing that I do want to note is to make sure that you send only a max of a 7 digit DMR ID when going to XLX, your repeater ID has 9 digits. Try setting the repeater ID to something like 1234567 (if you don't have a second DMR ID) and test again. I'm not sure if using that ID is copacetic with every network, but it shouldn't be a problem with XLX since I think it only uses the repeater ID to lookup and display the callsign of the network you're coming in on. Your mileage may vary, caveat emptor, don't forget to turn the lights off before you leave, etc.

I would be very interested in how the test runs with that change.

Steve KC1AWV





Re: 1 Way Audio (XLX DMR to ASL)

Steve KC1AWV
 

Ok, unless someone else can provide clues as to what might be happening I may have to lab this and go through the steps again to recreate and solve. I plan on restructuring the system I run here this weekend anyway, so it may be a good chance to write this stuff down for future reference.

On Wed, Mar 27, 2019 at 9:58 PM Daniel L. Srebnick <dan@...> wrote:
Steve:

I changed the repeater id in Analog_Bridge.ini to 1234567 as you suggested. After restarting all the involved processes, my test results were unchanged.

On Wed, 2019-03-27 at 20:48 -0400, Steve KC1AWV wrote:
Daniel,

I've had the same issue myself before. I'm trying to remember exactly what I did to rectify the problem, but it's been a while since the last time I played with the configurations here. One thing that I do want to note is to make sure that you send only a max of a 7 digit DMR ID when going to XLX, your repeater ID has 9 digits. Try setting the repeater ID to something like 1234567 (if you don't have a second DMR ID) and test again. I'm not sure if using that ID is copacetic with every network, but it shouldn't be a problem with XLX since I think it only uses the repeater ID to lookup and display the callsign of the network you're coming in on. Your mileage may vary, caveat emptor, don't forget to turn the lights off before you leave, etc.

I would be very interested in how the test runs with that change.

Steve KC1AWV




--
Steve Miller
KC1AWV


Re: Asterisk Error

K4VL
 

As a matter of fact I bought two new cards. The second I plan on being a clone. 


On Wed, Mar 27, 2019, 7:56 PM Steve KC1AWV <smiller@...> wrote:
Glad to hear it! I would suggest to take an image of the known good card and back it up safely somewhere so you can slap it on a new card if this comes up again. But that might just be the paranoia here talking. :)

Steve KC1AWV

On Wed, Mar 27, 2019 at 7:13 PM K4VL <73dek4vl@...> wrote:
Thanks again for everybody's help. I bought a new SD card and got it reconfigured and working again.

73 de K4VL

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.



--
Steve Miller
KC1AWV


Re: 1 Way Audio (XLX DMR to ASL)

Dan K2IE
 

Steve:

I changed the repeater id in Analog_Bridge.ini to 1234567 as you suggested. After restarting all the involved processes, my test results were unchanged.

On Wed, 2019-03-27 at 20:48 -0400, Steve KC1AWV wrote:
Daniel,

I've had the same issue myself before. I'm trying to remember exactly what I did to rectify the problem, but it's been a while since the last time I played with the configurations here. One thing that I do want to note is to make sure that you send only a max of a 7 digit DMR ID when going to XLX, your repeater ID has 9 digits. Try setting the repeater ID to something like 1234567 (if you don't have a second DMR ID) and test again. I'm not sure if using that ID is copacetic with every network, but it shouldn't be a problem with XLX since I think it only uses the repeater ID to lookup and display the callsign of the network you're coming in on. Your mileage may vary, caveat emptor, don't forget to turn the lights off before you leave, etc.

I would be very interested in how the test runs with that change.

Steve KC1AWV



Re: Asterisk Error

Steve KC1AWV
 

Glad to hear it! I would suggest to take an image of the known good card and back it up safely somewhere so you can slap it on a new card if this comes up again. But that might just be the paranoia here talking. :)

Steve KC1AWV


On Wed, Mar 27, 2019 at 7:13 PM K4VL <73dek4vl@...> wrote:
Thanks again for everybody's help. I bought a new SD card and got it reconfigured and working again.

73 de K4VL

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.



--
Steve Miller
KC1AWV


Re: 1 Way Audio (XLX DMR to ASL)

Steve KC1AWV
 

Daniel,

I've had the same issue myself before. I'm trying to remember exactly what I did to rectify the problem, but it's been a while since the last time I played with the configurations here. One thing that I do want to note is to make sure that you send only a max of a 7 digit DMR ID when going to XLX, your repeater ID has 9 digits. Try setting the repeater ID to something like 1234567 (if you don't have a second DMR ID) and test again. I'm not sure if using that ID is copacetic with every network, but it shouldn't be a problem with XLX since I think it only uses the repeater ID to lookup and display the callsign of the network you're coming in on. Your mileage may vary, caveat emptor, don't forget to turn the lights off before you leave, etc.

I would be very interested in how the test runs with that change.

Steve KC1AWV


On Wed, Mar 27, 2019 at 4:04 PM Daniel L. Srebnick <dan@...> wrote:
Just to clarify the diagram below, the md380-emu hangs off the Analog Bridge...should have used a fixed font.

On Wed, 2019-03-27 at 12:13 -0700, Daniel L. Srebnick wrote:
I am trying to gateway ASL to XLX DMR.  Here is a diagram of what I have implemented.

Cloud Server 1

ASL Asterisk (Pvt Node and Public Node) <===> Analog Bridge <===> MMDVM Bridge <===> DMR Gateway (from github)
                                                                                      ||
                                                                                      ||
                                                                                md380-emu

Cloud Server 2

xlxd based reflector


I can successfully pass audio from the DMR side to the Asterisk side of the connection.  Quality is good.  However, when I try to pass audio from Asterisk to DMR, it sets up the path but there is no audio.  The DMR side times out after about 2 seconds after Analog PTT, the ID number of the gateway shows up on the screen, and that is all.

What should I look at next?

Here are some log snippets from a successful DMR <==> Analog transmission:

MMDVM Bridge:
M: 2019-03-27 19:03:19.379 DMR Slot 2, received network voice header from K2DLS to TG 6
M: 2019-03-27 19:03:23.554 DMR Slot 2, received network end of voice transmission, 4.0 seconds, 0% packet loss, BER: 0.0%

Analog Bridge:

I: 2019-03-27 19:02:34.163 Begin TX: src=3134090 rpt=0 dst=6 slot=2 cc=0
D: 2019-03-27 19:02:37.225 End TX

Here are snippers from the unsuccesful Analog <==> DMR:

MMDVM Bridge:

M: 2019-03-27 19:04:10.405 DMR, TX state = ON
I: 2019-03-27 19:04:10.405 DMR, Begin TX: src=3134090 rpt=313409003 dst=6 slot=2 cc=1 metadata=K2DLS
M: 2019-03-27 19:04:14.262 DMR, TX state = OFF

Analog Bridge:

M: 2019-03-27 19:04:10.403 PTT on
D: 2019-03-27 19:04:14.259 cpu_time_used = 3856, minTxTime = 2000, pttTime = 1553713450403, end = 1553713454259
M: 2019-03-27 19:04:14.259 PTT off (keyed for 3856 ms)

DMR Gateway:

No useful logging for XLX seen after the connect with the level set to 1.

xlxd: Lots of these going from analog to DMR...

Mar 27 14:58:22 somehost xlxd[8847]: WARNING: orphaned DvFramePacket SID 56803 from 1.2.3.4
Mar 27 14:58:23 somehost xlxd[8847]: WARNING: orphaned DvFramePacket SID 56803 from 1.2.3.4
Mar 27 14:58:23 somehost xlxd[8847]: WARNING: orphaned DvFramePacket SID 56803 from 1.2.3.4
Mar 27 14:58:23 somehost xlxd[8847]: WARNING: orphaned DvFramePacket SID 56803 from 1.2.3.4
Mar 27 14:58:23 somehost xlxd[8847]: WARNING: orphaned DvFramePacket SID 56803 from 1.2.3.4

A fellow ham in the local area also had this exact problem.

Suggestions appreciated.

73,

Dan Srebnick
K2DLS



--
Steve Miller
KC1AWV


Re: Asterisk Error

K4VL
 

Thanks again for everybody's help. I bought a new SD card and got it reconfigured and working again.

73 de K4VL

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.


Re: 1 Way Audio (XLX DMR to ASL)

Dan K2IE
 

Just to clarify the diagram below, the md380-emu hangs off the Analog Bridge...should have used a fixed font.

On Wed, 2019-03-27 at 12:13 -0700, Daniel L. Srebnick wrote:
I am trying to gateway ASL to XLX DMR.  Here is a diagram of what I have implemented.

Cloud Server 1

ASL Asterisk (Pvt Node and Public Node) <===> Analog Bridge <===> MMDVM Bridge <===> DMR Gateway (from github)
                                                                                      ||
                                                                                      ||
                                                                                md380-emu

Cloud Server 2

xlxd based reflector


I can successfully pass audio from the DMR side to the Asterisk side of the connection.  Quality is good.  However, when I try to pass audio from Asterisk to DMR, it sets up the path but there is no audio.  The DMR side times out after about 2 seconds after Analog PTT, the ID number of the gateway shows up on the screen, and that is all.

What should I look at next?

Here are some log snippets from a successful DMR <==> Analog transmission:

MMDVM Bridge:
M: 2019-03-27 19:03:19.379 DMR Slot 2, received network voice header from K2DLS to TG 6
M: 2019-03-27 19:03:23.554 DMR Slot 2, received network end of voice transmission, 4.0 seconds, 0% packet loss, BER: 0.0%

Analog Bridge:

I: 2019-03-27 19:02:34.163 Begin TX: src=3134090 rpt=0 dst=6 slot=2 cc=0
D: 2019-03-27 19:02:37.225 End TX

Here are snippers from the unsuccesful Analog <==> DMR:

MMDVM Bridge:

M: 2019-03-27 19:04:10.405 DMR, TX state = ON
I: 2019-03-27 19:04:10.405 DMR, Begin TX: src=3134090 rpt=313409003 dst=6 slot=2 cc=1 metadata=K2DLS
M: 2019-03-27 19:04:14.262 DMR, TX state = OFF

Analog Bridge:

M: 2019-03-27 19:04:10.403 PTT on
D: 2019-03-27 19:04:14.259 cpu_time_used = 3856, minTxTime = 2000, pttTime = 1553713450403, end = 1553713454259
M: 2019-03-27 19:04:14.259 PTT off (keyed for 3856 ms)

DMR Gateway:

No useful logging for XLX seen after the connect with the level set to 1.

xlxd: Lots of these going from analog to DMR...

Mar 27 14:58:22 somehost xlxd[8847]: WARNING: orphaned DvFramePacket SID 56803 from 1.2.3.4
Mar 27 14:58:23 somehost xlxd[8847]: WARNING: orphaned DvFramePacket SID 56803 from 1.2.3.4
Mar 27 14:58:23 somehost xlxd[8847]: WARNING: orphaned DvFramePacket SID 56803 from 1.2.3.4
Mar 27 14:58:23 somehost xlxd[8847]: WARNING: orphaned DvFramePacket SID 56803 from 1.2.3.4
Mar 27 14:58:23 somehost xlxd[8847]: WARNING: orphaned DvFramePacket SID 56803 from 1.2.3.4

A fellow ham in the local area also had this exact problem.

Suggestions appreciated.

73,

Dan Srebnick
K2DLS


1 Way Audio (XLX DMR to ASL)

Dan K2IE
 

I am trying to gateway ASL to XLX DMR.  Here is a diagram of what I have implemented.

Cloud Server 1

ASL Asterisk (Pvt Node and Public Node) <===> Analog Bridge <===> MMDVM Bridge <===> DMR Gateway (from github)
                                                                                      ||
                                                                                      ||
                                                                                md380-emu

Cloud Server 2

xlxd based reflector


I can successfully pass audio from the DMR side to the Asterisk side of the connection.  Quality is good.  However, when I try to pass audio from Asterisk to DMR, it sets up the path but there is no audio.  The DMR side times out after about 2 seconds after Analog PTT, the ID number of the gateway shows up on the screen, and that is all.

What should I look at next?

Here are some log snippets from a successful DMR <==> Analog transmission:

MMDVM Bridge:
M: 2019-03-27 19:03:19.379 DMR Slot 2, received network voice header from K2DLS to TG 6
M: 2019-03-27 19:03:23.554 DMR Slot 2, received network end of voice transmission, 4.0 seconds, 0% packet loss, BER: 0.0%

Analog Bridge:

I: 2019-03-27 19:02:34.163 Begin TX: src=3134090 rpt=0 dst=6 slot=2 cc=0
D: 2019-03-27 19:02:37.225 End TX

Here are snippers from the unsuccesful Analog <==> DMR:

MMDVM Bridge:

M: 2019-03-27 19:04:10.405 DMR, TX state = ON
I: 2019-03-27 19:04:10.405 DMR, Begin TX: src=3134090 rpt=313409003 dst=6 slot=2 cc=1 metadata=K2DLS
M: 2019-03-27 19:04:14.262 DMR, TX state = OFF

Analog Bridge:

M: 2019-03-27 19:04:10.403 PTT on
D: 2019-03-27 19:04:14.259 cpu_time_used = 3856, minTxTime = 2000, pttTime = 1553713450403, end = 1553713454259
M: 2019-03-27 19:04:14.259 PTT off (keyed for 3856 ms)

DMR Gateway:

No useful logging for XLX seen after the connect with the level set to 1.

xlxd: Lots of these going from analog to DMR...

Mar 27 14:58:22 somehost xlxd[8847]: WARNING: orphaned DvFramePacket SID 56803 from 1.2.3.4
Mar 27 14:58:23 somehost xlxd[8847]: WARNING: orphaned DvFramePacket SID 56803 from 1.2.3.4
Mar 27 14:58:23 somehost xlxd[8847]: WARNING: orphaned DvFramePacket SID 56803 from 1.2.3.4
Mar 27 14:58:23 somehost xlxd[8847]: WARNING: orphaned DvFramePacket SID 56803 from 1.2.3.4
Mar 27 14:58:23 somehost xlxd[8847]: WARNING: orphaned DvFramePacket SID 56803 from 1.2.3.4

A fellow ham in the local area also had this exact problem.

Suggestions appreciated.

73,

Dan Srebnick
K2DLS


Re: Asterisk Error

K4VL
 

Root is using 12% and tmpfs is using 11%


On Wed, Mar 27, 2019 at 12:30 PM Mark N2NUO <n2nuo@...> wrote:

Just a thought,

When you sat up this pi, did you expand the file system after installing the OS?

What does df show for disk usage?

I am thinking that you may be out of disk space, but only a theory at this time.

Mark

On 3/26/19 10:29 PM, K4VL wrote:
BTW I'm getting the same error when I look at the status of mmdvm_bridge. analog_bridge is running.


Re: Asterisk Error

Mark N2NUO <n2nuo@...>
 

Just a thought,

When you sat up this pi, did you expand the file system after installing the OS?

What does df show for disk usage?

I am thinking that you may be out of disk space, but only a theory at this time.

Mark

On 3/26/19 10:29 PM, K4VL wrote:
BTW I'm getting the same error when I look at the status of mmdvm_bridge. analog_bridge is running.


Re: Asterisk Error

K4VL
 

Thanks I will test that out on my new sdcard this evening.

Virus-free. www.avg.com


On Wed, Mar 27, 2019 at 7:38 AM Steve KC1AWV <smiller@...> wrote:
SFTP is an FTP protocol that uses encryption over the wire. So, yes you'll need to have an FTP server running to use FTP. However, WinSCP also can use SCP which only needs an ssh server running, which it sounds like you already do, in order to log into the Pi. Instead of using SFTP, log into the Pi with WinSCP, make sure the protocol is set to SCP, and use the standard SSH port, 22. Then, you should be able to browse the remote machine and drag 'n drop the files over to your local computer.

The other option is to just do a direct copy/paste from a terminal like putty, just cat the file to the terminal and copy/paste to notepad or the like. That's how I usually do a quick copy of a log or a conf file.

root@allstar:/home/smiller# cat /etc/asterisk/rpt.conf

will print the rpt configuration file out to the terminal, and I just copy/paste it to notepad. If the file has a lot of lines in it, you may exceed the terminal buffer and cut off a chunk of the file, so copying it using SCP may be easier at that point.

Screenshot of the WinSCP login window attached.

On Wed, Mar 27, 2019 at 8:23 AM K4VL <73dek4vl@...> wrote:
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



--
Steve Miller
KC1AWV


Re: Asterisk Error

Steve KC1AWV
 

SFTP is an FTP protocol that uses encryption over the wire. So, yes you'll need to have an FTP server running to use FTP. However, WinSCP also can use SCP which only needs an ssh server running, which it sounds like you already do, in order to log into the Pi. Instead of using SFTP, log into the Pi with WinSCP, make sure the protocol is set to SCP, and use the standard SSH port, 22. Then, you should be able to browse the remote machine and drag 'n drop the files over to your local computer.

The other option is to just do a direct copy/paste from a terminal like putty, just cat the file to the terminal and copy/paste to notepad or the like. That's how I usually do a quick copy of a log or a conf file.

root@allstar:/home/smiller# cat /etc/asterisk/rpt.conf

will print the rpt configuration file out to the terminal, and I just copy/paste it to notepad. If the file has a lot of lines in it, you may exceed the terminal buffer and cut off a chunk of the file, so copying it using SCP may be easier at that point.

Screenshot of the WinSCP login window attached.

On Wed, Mar 27, 2019 at 8:23 AM K4VL <73dek4vl@...> wrote:
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



--
Steve Miller
KC1AWV

5941 - 5960 of 9595