cp: cannot stat `ezstream.xml': No such file or directory

And from there it starts it seems.

Ok for some reason it's not in the right spot or can't read the file.

Checklist says check ownership and permissions and if file is where it's supposed to be or is a setting there out of wack?

With any luck after sorting that the rest might come good ;-) touch wood.

Just a guess on my wild behalf that or the file could be corrupt (unlikely) Or file locking has occurred due to some stupid non apparent reason.

Well usually there is a good reason eg a session crashed and text editor or even program in question didn't get time to shut the file proper.

That one probably being the biggest aherm.

I have put the call out to those who use Broadcastify that I know of to see if they could spot the problem straight of

and if so to contact you.

Hope that helps.

On 27 October 2014 03:01, Loren Tedford <lorentedford@gmail.com> wrote:

copy to /etc/asterisk/rpt.conf (below node#) aka first section.
outstreamcmd=/bin/sh,-c,/usr/bin/lame --preset cbr 16 -r -m m -s 8 --bitwidth 16 - - | /usr/bin/ezstream -c /etc/ezstream.xml
cp: cannot stat `ezstream.xml': No such file or directory
cp: `bin/awk' and `/usr/bin/awk' are the same file
cp: `bin/cut' and `/usr/bin/cut' are the same file
cp: `bin/env' and `/usr/bin/env' are the same file
cp: `bin/gawk' and `/usr/bin/gawk' are the same file
cp: `bin/gettext' and `/usr/bin/gettext' are the same file
cp: `bin/gunzip' and `/usr/bin/gunzip' are the same file
cp: `bin/gzip' and `/usr/bin/gzip' are the same file
cp: `bin/kill' and `/usr/bin/kill' are the same file
cp: `bin/ksh' and `/usr/bin/ksh' are the same file
cp: `bin/logger' and `/usr/bin/logger' are the same file
cp: cannot stat `share/man/man1/*': No such file or directory
cp: cannot stat `/share/doc/ez*': No such file or directory

Followed these directions below..

1.) Extract the attached file EZS.tgz

2.) Run 'sh EZS'

3.) Agree to everything - yes

4.) Modify the /etc/ezstream.xml file - replacing the ######'s with the
correct
mount point/password/name of your stream. (These details are provided by
radioreference.com when you sign up to do a stream FREE (under the
"Technicals" tab in the stream management section.)

5.) add the following to your /etc/asterisk/rpt.conf in the first section
ex: above the status reporting section.
"outstreamcmd=/bin/sh,-c,/usr/bin/lame --preset cbr 16 -r -m m -s 8
--bitwidth 16 - - | /usr/bin/ezstream -qvc /etc/ezstream.xml"

*This should be all on one line ^^^*
You may change the ezstream.xml name if you wish but also do so in the /etc
dir, ex: if you had multiple streams/nodes to stream from.
This setup is per node.

btw sometimes I have had to set a cron to kill the ezstream each week or so
- has not been an issue lately if you do notice it failing, the command is
'kill -9 $(pgrep ezstream)&' This will not break/stop ezstream but should
restart it...

Here is example of what it looks like in rpt.conf

[29925] ; Change this to your assigned node num$
rxchannel=Radio/usb29925
outstreamcmd=/bin/sh,-c,/usr/bin/lame --preset cbr 16 -r -m m -s 8 --bitwidth 16 - - | /usr/bin/ezstream -c /etc/ezstream.xml
duplex=2

Example of node number two same config
[27103] ; Change this to your assigned node num$
rxchannel=Radio/usb27103
outstreamcmd=/bin/sh,-c,/usr/bin/lame --preset cbr 16 -r -m m -s 8 --bitwidth 16 - - | /usr/bin/ezstream -c /etc/ezstream2.xml
duplex=2

Ez stream still not working even with the correct information in the ezstream.xml files located in /etc/

Kinda lost now what steps i have missed..

Loren Tedford (KC9ZHV)

_______________________________________________
App_rpt-users mailing list
App_rpt-users@ohnosec.org
http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"
You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.