Centova Technologies Forum

Centova Cast v3 => Bugs and issues => Topic started by: gutoeterno on December 21, 2012, 09:50:38 am

Title: broadcasters restart all the time and I get several emails saying restarted.
Post by: gutoeterno on December 21, 2012, 09:50:38 am
Hello Steve, or someone who has gone through this.
Already installed Centovacast v3 with v2 Shoutcast more than ten times in my server CentOS 5.8 and still this problem always happens.

My broadcasters always restart automatically and get these emails:

sertanejogeral,

This message is to inform you That your streaming server went down in the past few minutes, but Has Been restarted successfully.

This message is for informational purposes only, and no action is required on your part.

Sincerely,

Streaming Centovacast RESERVE - Well Technology Server Monitor

I've read some posts that said that Steve could be two files sc_trans plumb the server, but it did not teach how to find and delete this file.

Please tell me step by step what I have to do to solve this problem.

I have another server CentOS 5.8 with the Centovacast V3 installed with Shoutcast V1 and works perfect.
Title: Re: broadcasters restart all the time and I get several emails saying restarted.
Post by: gutoeterno on December 21, 2012, 11:07:47 am
Look, I performed what Steve said in this post:

http://forums.centova.com/index.php?topic=2061.0

I ran it on my server shoutcast v2 witch centovacast v3:

"" You'd need to run 'ps aux' and find the PID of the sctrans2 process, then run 'kill -9 <pid>' replacing <pid> with the actual PID number. ""

I found these in my server PID:
ccuser   20590  2.2  0.7 191620  8112 ?        Sl   15:34   2:00 /usr/local/centovacast/sctrans2/sc_trans ../sertanejogeral/etc/sourc

ccuser   22944 19.8  0.7 191040  7804 ?        Sl   17:03   0:02 /usr/local/centovacast/sctrans2/sc_trans ../lovenight/etc/source.con

So I ran the command to kill the process after the two webradios rebooted, but still keeps rebooting.

What to do?

Title: Re: broadcasters restart all the time and I get several emails saying restarted.
Post by: Centova - Steve B. on December 21, 2012, 03:02:23 pm
You'll need to check your sc_trans logs to find out why it's exiting.  The post you quoted contains instructions for when your autoDJ is running but showing as offline -- it's unrelated to what you described here.
Title: Re: broadcasters restart all the time and I get several emails saying restarted.
Post by: gutoeterno on December 22, 2012, 03:50:05 am
Hello, but tell me how to check these logs. I do not know how to do that. Please help me Steve.
Title: Re: broadcasters restart all the time and I get several emails saying restarted.
Post by: gutoeterno on December 22, 2012, 04:04:20 am
I went into this folder and it is empty, what to do?

/usr/local/centovacast/sctrans2/logs
Title: Re: broadcasters restart all the time and I get several emails saying restarted.
Post by: gutoeterno on December 24, 2012, 05:37:26 am
Hello please ???
Title: Re: broadcasters restart all the time and I get several emails saying restarted.
Post by: gutoeterno on December 26, 2012, 03:26:15 pm
POR FAVOR, ALGUEM ME AJUDE POR FAVOR !

PLEASE SOMEONE HELP ME PLEASE!
Title: Re: broadcasters restart all the time and I get several emails saying restarted.
Post by: DrO on December 27, 2012, 02:27:29 am
you've been told what to do by looking in the sc_trans logs which is typically a file called sc_trans.log on the machine (i don't know where it's located in a Centova setup but you should be able to search for that filename on the host being used).

and you're likely not getting a reply due to people being away on holiday (considering the time of the year).

-daz
Title: Re: broadcasters restart all the time and I get several emails saying restarted.
Post by: gutoeterno on December 27, 2012, 07:50:42 am
My dear, I said that this file does not exist, have already searched the entire server.
So do not give me this bullshit.

If you do not want to help, please do not disturb.

Talking seriously.
Title: Re: broadcasters restart all the time and I get several emails saying restarted.
Post by: DrO on December 27, 2012, 08:30:27 am
i did want to help but i'll do as you wish as it's not like you needed the current developer of sc_trans (me) to try to help out with your issue anyway (once you'd worked out where Centova is placing the log file).
Title: Re: broadcasters restart all the time and I get several emails saying restarted.
Post by: gutoeterno on December 27, 2012, 02:16:40 pm
And you call what you said before help?
The concept here of this forum is to share knowledge because everyone here in the community we are testing (and paying monthly) by a beta that still has many problems and the idea of this forum is that the community help each other and not criticism about who will respond or claim to be year-end, seriously.
Title: Re: broadcasters restart all the time and I get several emails saying restarted.
Post by: megadealhosting on December 29, 2012, 01:30:26 am
whilst i find the OP language and attitude abhorrent, i CAN understand their frustration.

we have djs that go live every night and as soon as they disconnect and the autoDJ is engaged i start getting the same email every ten minutes telling me that the server has restarted.

ive searched the server for sc_trans.log and it just does not exist, therefore I am at a loss (like the OP) as to where to start looking for diagnostics.

i can kill the processes running which are causing the issue, restart the server and this resolves it until another DJ logs in, does their show and logs out again.

but not being able to find the log file anywhere on the server doesnt help in the slightest.
Title: Re: broadcasters restart all the time and I get several emails saying restarted.
Post by: gutoeterno on January 02, 2013, 12:31:09 pm
is exactly what I'm saying, this file does not exist on the server sc_trans.log.
really do not know what Steve meant by it, the worse it takes days or even weeks to help us, I know he must be a busy guy extrimamente, but I believe the Contove should have a little more respect for us , we pay them monthly for the program, and even if we pay a beta tested at 2 years, I think they should have more people to help us with the problems of this new version.

really do not know what to do, the license free version will expire and I will have to buy the license to try this new version continues to be using today and can not figure out for what reason the Shoutcast V2 restarts all the time without stopping.
Title: Re: broadcasters restart all the time and I get several emails saying restarted.
Post by: streampakket on January 02, 2013, 02:08:37 pm
Hi ive had this problem before and this is what i did.

login to ssh and run ps aux
find the pid for the sctrans and kill that proces, then reboot youre server.

Title: Re: broadcasters restart all the time and I get several emails saying restarted.
Post by: gutoeterno on January 02, 2013, 03:31:02 pm
Hello streampakket

Please be more specific, I did this procedure but to no avail.
Not that you found this sctrans said.

Help me please with details.
Title: Re: broadcasters restart all the time and I get several emails saying restarted.
Post by: gutoeterno on January 02, 2013, 03:36:41 pm
LOOK DETAILS PLEASE:

[root@SRV-CENTOVACAST ~]# ps aux
USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root         1  0.6  0.0   2168   632 ?        Ss   21:23   0:02 init [3]                                                           
root         2  0.0  0.0      0     0 ?        S<   21:23   0:00 [migration/0]
root         3  0.0  0.0      0     0 ?        SN   21:23   0:00 [ksoftirqd/0]
root         4  0.0  0.0      0     0 ?        S<   21:23   0:00 [watchdog/0]
root         5  0.0  0.0      0     0 ?        S<   21:23   0:00 [migration/1]
root         6  0.0  0.0      0     0 ?        SN   21:23   0:00 [ksoftirqd/1]
root         7  0.0  0.0      0     0 ?        S<   21:23   0:00 [watchdog/1]
root         8  0.0  0.0      0     0 ?        S<   21:23   0:00 [migration/2]
root         9  0.0  0.0      0     0 ?        SN   21:23   0:00 [ksoftirqd/2]
root        10  0.0  0.0      0     0 ?        S<   21:23   0:00 [watchdog/2]
root        11  0.0  0.0      0     0 ?        S<   21:23   0:00 [migration/3]
root        12  0.0  0.0      0     0 ?        SN   21:23   0:00 [ksoftirqd/3]
root        13  0.0  0.0      0     0 ?        S<   21:23   0:00 [watchdog/3]
root        14  0.0  0.0      0     0 ?        S<   21:23   0:00 [migration/4]
root        15  0.0  0.0      0     0 ?        SN   21:23   0:00 [ksoftirqd/4]
root        16  0.0  0.0      0     0 ?        S<   21:23   0:00 [watchdog/4]
root        17  0.0  0.0      0     0 ?        S<   21:23   0:00 [migration/5]
root        18  0.0  0.0      0     0 ?        SN   21:23   0:00 [ksoftirqd/5]
root        19  0.0  0.0      0     0 ?        S<   21:23   0:00 [watchdog/5]
root        20  0.0  0.0      0     0 ?        S<   21:23   0:00 [migration/6]
root        21  0.0  0.0      0     0 ?        SN   21:23   0:00 [ksoftirqd/6]
root        22  0.0  0.0      0     0 ?        S<   21:23   0:00 [watchdog/6]
root        23  0.0  0.0      0     0 ?        S<   21:23   0:00 [migration/7]
root        24  0.0  0.0      0     0 ?        SN   21:23   0:00 [ksoftirqd/7]
root        25  0.0  0.0      0     0 ?        S<   21:23   0:00 [watchdog/7]
root        26  0.0  0.0      0     0 ?        S<   21:23   0:00 [migration/8]
root        27  0.0  0.0      0     0 ?        SN   21:23   0:00 [ksoftirqd/8]
root        28  0.0  0.0      0     0 ?        S<   21:23   0:00 [watchdog/8]
root        29  0.0  0.0      0     0 ?        S<   21:23   0:00 [migration/9]
root        30  0.0  0.0      0     0 ?        SN   21:23   0:00 [ksoftirqd/9]
root        31  0.0  0.0      0     0 ?        S<   21:23   0:00 [watchdog/9]
root        32  0.0  0.0      0     0 ?        S<   21:23   0:00 [migration/10]
root        33  0.0  0.0      0     0 ?        SN   21:23   0:00 [ksoftirqd/10]
root        34  0.0  0.0      0     0 ?        S<   21:23   0:00 [watchdog/10]
root        35  0.0  0.0      0     0 ?        S<   21:23   0:00 [migration/11]
root        36  0.0  0.0      0     0 ?        SN   21:23   0:00 [ksoftirqd/11]
root        37  0.0  0.0      0     0 ?        S<   21:23   0:00 [watchdog/11]
root        38  0.0  0.0      0     0 ?        S<   21:23   0:00 [events/0]
root        39  0.0  0.0      0     0 ?        S<   21:23   0:00 [events/1]
root        40  0.0  0.0      0     0 ?        S<   21:23   0:00 [events/2]
root        41  0.0  0.0      0     0 ?        S<   21:23   0:00 [events/3]
root        42  0.0  0.0      0     0 ?        S<   21:23   0:00 [events/4]
root        43  0.0  0.0      0     0 ?        S<   21:23   0:00 [events/5]
root        44  0.0  0.0      0     0 ?        S<   21:23   0:00 [events/6]
root        45  0.0  0.0      0     0 ?        S<   21:23   0:00 [events/7]
root        46  0.0  0.0      0     0 ?        S<   21:23   0:00 [events/8]
root        47  0.0  0.0      0     0 ?        S<   21:23   0:00 [events/9]
root        48  0.0  0.0      0     0 ?        S<   21:23   0:00 [events/10]
root        49  0.0  0.0      0     0 ?        S<   21:23   0:00 [events/11]
root        50  0.0  0.0      0     0 ?        S<   21:23   0:00 [khelper]
root        51  0.0  0.0      0     0 ?        S<   21:23   0:00 [kthread]
Title: Re: broadcasters restart all the time and I get several emails saying restarted.
Post by: gutoeterno on January 02, 2013, 03:37:20 pm
AND......

root        65  0.0  0.0      0     0 ?        S<   21:23   0:00 [kblockd/0]
root        66  0.0  0.0      0     0 ?        S<   21:23   0:00 [kblockd/1]
root        67  0.0  0.0      0     0 ?        S<   21:23   0:00 [kblockd/2]
root        68  0.0  0.0      0     0 ?        S<   21:23   0:00 [kblockd/3]
root        69  0.0  0.0      0     0 ?        S<   21:23   0:00 [kblockd/4]
root        70  0.0  0.0      0     0 ?        S<   21:23   0:00 [kblockd/5]
root        71  0.0  0.0      0     0 ?        S<   21:23   0:00 [kblockd/6]
root        72  0.0  0.0      0     0 ?        S<   21:23   0:00 [kblockd/7]
root        73  0.0  0.0      0     0 ?        S<   21:23   0:00 [kblockd/8]
root        74  0.0  0.0      0     0 ?        S<   21:23   0:00 [kblockd/9]
root        75  0.0  0.0      0     0 ?        S<   21:23   0:00 [kblockd/10]
root        76  0.0  0.0      0     0 ?        S<   21:23   0:00 [kblockd/11]
root        77  0.0  0.0      0     0 ?        S<   21:23   0:00 [kacpid]
root       143  0.0  0.0      0     0 ?        S<   21:23   0:00 [cqueue/0]
root       144  0.0  0.0      0     0 ?        S<   21:23   0:00 [cqueue/1]
root       145  0.0  0.0      0     0 ?        S<   21:23   0:00 [cqueue/2]
root       146  0.0  0.0      0     0 ?        S<   21:23   0:00 [cqueue/3]
root       147  0.0  0.0      0     0 ?        S<   21:23   0:00 [cqueue/4]
root       148  0.0  0.0      0     0 ?        S<   21:23   0:00 [cqueue/5]
root       149  0.0  0.0      0     0 ?        S<   21:23   0:00 [cqueue/6]
root       150  0.0  0.0      0     0 ?        S<   21:23   0:00 [cqueue/7]
root       151  0.0  0.0      0     0 ?        S<   21:23   0:00 [cqueue/8]
root       152  0.0  0.0      0     0 ?        S<   21:23   0:00 [cqueue/9]
root       153  0.0  0.0      0     0 ?        S<   21:23   0:00 [cqueue/10]
root       154  0.0  0.0      0     0 ?        S<   21:23   0:00 [cqueue/11]
root       157  0.0  0.0      0     0 ?        S<   21:23   0:00 [khubd]
root       159  0.0  0.0      0     0 ?        S<   21:23   0:00 [kseriod]
root       280  0.0  0.0      0     0 ?        S    21:23   0:00 [khungtaskd]
root       281  0.0  0.0      0     0 ?        S    21:23   0:00 [pdflush]
root       282  0.0  0.0      0     0 ?        S    21:23   0:00 [pdflush]
root       283  0.0  0.0      0     0 ?        S<   21:23   0:00 [kswapd0]
root       284  0.0  0.0      0     0 ?        S<   21:23   0:00 [aio/0]
root       285  0.0  0.0      0     0 ?        S<   21:23   0:00 [aio/1]
root       286  0.0  0.0      0     0 ?        S<   21:23   0:00 [aio/2]
root       287  0.0  0.0      0     0 ?        S<   21:23   0:00 [aio/3]
root       288  0.0  0.0      0     0 ?        S<   21:23   0:00 [aio/4]
root       289  0.0  0.0      0     0 ?        S<   21:23   0:00 [aio/5]
root       290  0.0  0.0      0     0 ?        S<   21:23   0:00 [aio/6]
root       291  0.0  0.0      0     0 ?        S<   21:23   0:00 [aio/7]
root       292  0.0  0.0      0     0 ?        S<   21:23   0:00 [aio/8]
root       293  0.0  0.0      0     0 ?        S<   21:23   0:00 [aio/9]
root       294  0.0  0.0      0     0 ?        S<   21:23   0:00 [aio/10]
root       295  0.0  0.0      0     0 ?        S<   21:23   0:00 [aio/11]
root       448  0.0  0.0      0     0 ?        S<   21:23   0:00 [kpsmoused]
root       560  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_con/0]
root       561  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_con/1]
root       562  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_con/2]
root       563  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_con/3]
root       564  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_con/4]
root       565  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_con/5]
root       566  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_con/6]
root       567  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_con/7]
root       568  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_con/8]
root       569  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_con/9]
root       570  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_con/10]
root       571  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_con/11]
root       572  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/0]
root       573  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/1]
root       574  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/2]
root       575  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/3]
root       576  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/4]
root       577  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/5]
root       578  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/6]
root       579  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/7]
root       580  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/8]
root       581  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/9]
root       582  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/10]
root       583  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/11]
root       584  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/0]
root       585  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/1]
root       586  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/2]
root       587  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/3]
root       588  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/4]
root       589  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/5]
root       590  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/6]
root       591  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/7]
root       592  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/8]
root       593  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/9]
root       594  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/10]
root       595  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/11]
root       596  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/0]
root       597  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/1]
root       598  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/2]
root       599  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/3]
root       600  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/4]
root       601  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/5]
root       602  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/6]
root       603  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/7]
root       604  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/8]
root       605  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/9]
root       606  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/10]
root       607  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/11]
root       608  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/0]
root       609  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/1]
root       610  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/2]
root       611  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/3]
root       612  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/4]
root       613  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/5]
root       614  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/6]
root       615  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/7]
root       616  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/8]
root       617  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/9]
root       618  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/10]
root       619  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/11]
root       620  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/0]
root       621  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/1]
root       622  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/2]
root       623  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/3]
root       624  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/4]
root       625  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/5]
root       626  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/6]
root       627  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/7]
root       628  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/8]
root       629  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/9]
root       630  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/10]
root       631  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/11]
root       632  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/0]
root       633  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/1]
root       634  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/2]
root       635  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/3]
root       636  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/4]
root       637  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/5]
root       638  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/6]
root       639  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/7]
root       640  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/8]
root       641  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/9]
root       642  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/10]
root       643  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/11]
root       644  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/0]
root       645  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/1]
root       646  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/2]
root       647  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/3]
root       648  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/4]
root       649  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/5]
root       650  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/6]
root       651  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/7]
root       652  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/8]
root       653  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/9]
root       654  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/10]
root       655  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/11]
root       656  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/0]
root       657  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/1]
root       658  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/2]
root       659  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/3]
root       660  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/4]
root       661  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/5]
root       662  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/6]
root       663  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/7]
root       664  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/8]
root       665  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/9]
root       666  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/10]
root       667  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/11]
root       668  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/0]
root       669  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/1]
root       670  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/2]
root       671  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/3]
root       672  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/4]
root       673  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/5]
root       674  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/6]
root       675  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/7]
root       676  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/8]
root       677  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/9]
root       678  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/10]
root       679  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/11]
root       680  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/0]
root       681  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/1]
root       682  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/2]
root       683  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/3]
root       684  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/4]
root       685  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/5]
root       686  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/6]
root       687  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/7]
root       688  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/8]
root       689  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/9]
root       690  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/10]
root       691  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/11]
root       692  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/0]
root       693  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/1]
root       694  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/2]
root       695  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/3]
root       696  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/4]
root       697  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/5]
root       698  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/6]
root       699  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/7]
root       700  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/8]
root       701  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/9]
root       702  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/10]
root       703  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/11]
root       704  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/0]
root       705  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/1]
root       706  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/2]
root       707  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/3]
root       708  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/4]
root       709  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/5]
root       710  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/6]
root       711  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/7]
root       712  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/8]
root       713  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/9]
root       714  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/10]
root       715  0.0  0.0      0     0 ?        S<   21:23   0:00 [hv_vmbus_ctl/11]
Title: Re: broadcasters restart all the time and I get several emails saying restarted.
Post by: gutoeterno on January 02, 2013, 03:37:43 pm
AND.....

root       729  0.0  0.0      0     0 ?        S<   21:23   0:00 [scsi_eh_0]
root       730  0.0  0.0      0     0 ?        S<   21:23   0:00 [scsi_eh_1]
root       744  0.0  0.0      0     0 ?        S<   21:23   0:00 [ata/0]
root       745  0.0  0.0      0     0 ?        S<   21:23   0:00 [ata/1]
root       746  0.0  0.0      0     0 ?        S<   21:23   0:00 [ata/2]
root       747  0.0  0.0      0     0 ?        S<   21:23   0:00 [ata/3]
root       748  0.0  0.0      0     0 ?        S<   21:23   0:00 [ata/4]
root       749  0.0  0.0      0     0 ?        S<   21:23   0:00 [ata/5]
root       750  0.0  0.0      0     0 ?        S<   21:23   0:00 [ata/6]
root       751  0.0  0.0      0     0 ?        S<   21:23   0:00 [ata/7]
root       752  0.0  0.0      0     0 ?        S<   21:23   0:00 [ata/8]
root       753  0.0  0.0      0     0 ?        S<   21:23   0:00 [ata/9]
root       754  0.0  0.0      0     0 ?        S<   21:23   0:00 [ata/10]
root       755  0.0  0.0      0     0 ?        S<   21:23   0:00 [ata/11]
root       756  0.0  0.0      0     0 ?        S<   21:23   0:00 [ata_aux]
root       783  0.0  0.0      0     0 ?        S<   21:23   0:00 [kstriped]
root       836  0.0  0.0      0     0 ?        S<   21:23   0:00 [ksnapd]
root       891  0.0  0.0      0     0 ?        D<   21:24   0:00 [kjournald]
root       917  0.0  0.0      0     0 ?        S<   21:24   0:00 [kauditd]
root       950  0.0  0.0   2404   652 ?        S<s  21:24   0:00 /sbin/udevd -d
root      2230  0.0  0.0      0     0 ?        S<   21:24   0:00 [kmpathd/0]
root      2231  0.0  0.0      0     0 ?        S<   21:24   0:00 [kmpathd/1]
root      2232  0.0  0.0      0     0 ?        S<   21:24   0:00 [kmpathd/2]
root      2233  0.0  0.0      0     0 ?        S<   21:24   0:00 [kmpathd/3]
root      2234  0.0  0.0      0     0 ?        S<   21:24   0:00 [kmpathd/4]
root      2235  0.0  0.0      0     0 ?        S<   21:24   0:00 [kmpathd/5]
root      2236  0.0  0.0      0     0 ?        S<   21:24   0:00 [kmpathd/6]
root      2237  0.0  0.0      0     0 ?        S<   21:24   0:00 [kmpathd/7]
root      2238  0.0  0.0      0     0 ?        S<   21:24   0:00 [kmpathd/8]
root      2239  0.0  0.0      0     0 ?        S<   21:24   0:00 [kmpathd/9]
root      2240  0.0  0.0      0     0 ?        S<   21:24   0:00 [kmpathd/10]
root      2241  0.0  0.0      0     0 ?        S<   21:24   0:00 [kmpathd/11]
root      2242  0.0  0.0      0     0 ?        S<   21:24   0:00 [kmpath_handlerd]
root      2264  0.0  0.0      0     0 ?        S<   21:24   0:00 [kjournald]
root      2489  0.0  0.0      0     0 ?        S<   21:24   0:00 [iscsi_eh]
root      2639  0.0  0.0      0     0 ?        S<   21:24   0:00 [cnic_wq]
root      2653  0.0  0.0      0     0 ?        S<   21:24   0:00 [bnx2i_thread/0]
root      2654  0.0  0.0      0     0 ?        S<   21:24   0:00 [bnx2i_thread/1]
root      2655  0.0  0.0      0     0 ?        S<   21:24   0:00 [bnx2i_thread/2]
root      2657  0.0  0.0      0     0 ?        S<   21:24   0:00 [bnx2i_thread/3]
root      2658  0.0  0.0      0     0 ?        S<   21:24   0:00 [bnx2i_thread/4]
root      2659  0.0  0.0      0     0 ?        S<   21:24   0:00 [bnx2i_thread/5]
root      2660  0.0  0.0      0     0 ?        S<   21:24   0:00 [bnx2i_thread/6]
root      2661  0.0  0.0      0     0 ?        S<   21:24   0:00 [bnx2i_thread/7]
root      2662  0.0  0.0      0     0 ?        S<   21:24   0:00 [bnx2i_thread/8]
root      2663  0.0  0.0      0     0 ?        S<   21:24   0:00 [bnx2i_thread/9]
root      2664  0.0  0.0      0     0 ?        S<   21:24   0:00 [bnx2i_thread/10]
root      2665  0.0  0.0      0     0 ?        S<   21:24   0:00 [bnx2i_thread/11]
root      2699  0.0  0.0      0     0 ?        S<   21:24   0:00 [ib_addr]
root      2738  0.0  0.0      0     0 ?        S<   21:24   0:00 [ib_mcast]
root      2739  0.0  0.0      0     0 ?        S<   21:24   0:00 [ib_inform]
root      2740  0.0  0.0      0     0 ?        S<   21:24   0:00 [local_sa]
root      2755  0.0  0.0      0     0 ?        S<   21:24   0:00 [iw_cm_wq]
root      2769  0.0  0.0      0     0 ?        S<   21:24   0:00 [ib_cm/0]
root      2770  0.0  0.0      0     0 ?        S<   21:24   0:00 [ib_cm/1]
root      2771  0.0  0.0      0     0 ?        S<   21:24   0:00 [ib_cm/2]
root      2772  0.0  0.0      0     0 ?        S<   21:24   0:00 [ib_cm/3]
root      2773  0.0  0.0      0     0 ?        S<   21:24   0:00 [ib_cm/4]
root      2774  0.0  0.0      0     0 ?        S<   21:24   0:00 [ib_cm/5]
root      2775  0.0  0.0      0     0 ?        S<   21:24   0:00 [ib_cm/6]
root      2776  0.0  0.0      0     0 ?        S<   21:24   0:00 [ib_cm/7]
root      2777  0.0  0.0      0     0 ?        S<   21:24   0:00 [ib_cm/8]
root      2778  0.0  0.0      0     0 ?        S<   21:24   0:00 [ib_cm/9]
root      2779  0.0  0.0      0     0 ?        S<   21:24   0:00 [ib_cm/10]
root      2780  0.0  0.0      0     0 ?        S<   21:24   0:00 [ib_cm/11]
root      2794  0.0  0.0      0     0 ?        S<   21:24   0:00 [rdma_cm]
root      2831  0.0  3.1  32760 32744 ?        S<Lsl 21:24   0:00 iscsiuio
root      2837  0.0  0.0   2368   408 ?        Ss   21:24   0:00 iscsid
root      2838  0.0  0.2   2832  2824 ?        S<Ls 21:24   0:00 iscsid
root      3083  0.0  0.0  12644   756 ?        S<sl 21:24   0:00 auditd
root      3085  0.0  0.0  12176   680 ?        S<sl 21:24   0:00 /sbin/audispd
root      3118  0.0  0.0   1824   560 ?        Ss   21:24   0:00 syslogd -m 0
root      3121  0.0  0.0   1772   392 ?        Ss   21:24   0:00 klogd -x
root      3255  0.0  0.0   2572   380 ?        Ss   21:24   0:00 irqbalance
rpc       3288  0.0  0.0   1920   540 ?        Ss   21:24   0:00 portmap
root      3334  0.0  0.0      0     0 ?        S<   21:24   0:00 [rpciod/0]
root      3335  0.0  0.0      0     0 ?        S<   21:24   0:00 [rpciod/1]
root      3336  0.0  0.0      0     0 ?        S<   21:24   0:00 [rpciod/2]
root      3337  0.0  0.0      0     0 ?        S<   21:24   0:00 [rpciod/3]
root      3338  0.0  0.0      0     0 ?        S<   21:24   0:00 [rpciod/4]
root      3339  0.0  0.0      0     0 ?        S<   21:24   0:00 [rpciod/5]
root      3340  0.0  0.0      0     0 ?        S<   21:24   0:00 [rpciod/6]
root      3341  0.0  0.0      0     0 ?        S<   21:24   0:00 [rpciod/7]
root      3342  0.0  0.0      0     0 ?        S<   21:24   0:00 [rpciod/8]
root      3343  0.0  0.0      0     0 ?        S<   21:24   0:00 [rpciod/9]
root      3344  0.0  0.0      0     0 ?        S<   21:24   0:00 [rpciod/10]
root      3345  0.0  0.0      0     0 ?        S<   21:24   0:00 [rpciod/11]
rpcuser   3362  0.0  0.0   2080   812 ?        Ss   21:24   0:00 rpc.statd
root      3400  0.0  0.0   5976   664 ?        Ss   21:24   0:00 rpc.idmapd
dbus      3432  0.0  0.0   2860   872 ?        Ss   21:24   0:00 dbus-daemon --system
root      3457  0.0  0.0   2264   752 ?        Ss   21:24   0:00 /usr/sbin/hcid
root      3461  0.0  0.0   1840   488 ?        Ss   21:24   0:00 /usr/sbin/sdpd
root      3519  0.0  0.0      0     0 ?        S<   21:24   0:00 [krfcommd]
root      3564  0.0  0.1  12840  1256 ?        Ssl  21:24   0:00 pcscd
root      3579  0.0  0.0   1768   524 ?        Ss   21:24   0:00 /usr/sbin/acpid
68        3597  0.3  0.3   5836  3824 ?        Ss   21:24   0:00 hald
root      3598  0.0  0.0   3276   988 ?        S    21:24   0:00 hald-runner
68        3606  0.0  0.0   2116   816 ?        S    21:24   0:00 hald-addon-acpi: listening on acpid socket /var/run/acpid.socket
68        3612  0.0  0.0   2116   800 ?        S    21:24   0:00 hald-addon-keyboard: listening on /dev/input/event0
root      3624  0.1  0.0   2068   648 ?        S    21:24   0:00 hald-addon-storage: polling /dev/hdc
root      3655  0.0  0.0   2016   440 ?        Ss   21:24   0:00 /usr/bin/hidd --server
root      3705  0.0  0.1  27400  1380 ?        Ssl  21:24   0:00 automount
root      3730  0.0  0.0   2008   444 ?        Ss   21:24   0:00 /usr/sbin/hv_kvp_daemon
root      3748  0.0  0.1   7256  1044 ?        Ss   21:24   0:00 /usr/sbin/sshd
root      3768  0.0  0.0   2844   848 ?        Ss   21:24   0:00 xinetd -stayalive -pidfile /var/run/xinetd.pid
root      3806  0.0  0.1   4640  1196 ?        S    21:24   0:00 /bin/sh /usr/bin/mysqld_safe --datadir=/var/lib/mysql --socket=/var/
mysql     3853  0.0  1.9 137976 19724 ?        Sl   21:24   0:00 /usr/libexec/mysqld --basedir=/usr --datadir=/var/lib/mysql --user=m
root      3899  0.0  0.1   9392  1892 ?        Ss   21:24   0:00 sendmail: accepting connections
smmsp     3909  0.0  0.1   8300  1512 ?        Ss   21:24   0:00 sendmail: Queue runner@01:00:00 for /var/spool/clientmqueue
root      3924  0.0  0.0   2008   352 ?        Ss   21:24   0:00 gpm -m /dev/input/mice -t exps2
root      3939  0.0  1.1  31128 11788 ?        Ss   21:24   0:00 /usr/sbin/httpd
root      3953  0.0  0.1   5392  1108 ?        Ss   21:24   0:00 crond
xfs       3985  0.0  0.1   3944  1524 ?        Ss   21:24   0:00 xfs -droppriv -daemon
root      3999  0.0  0.0   1768   512 ?        SNs  21:24   0:00 anacron -s
root      4012  0.0  0.0   2368   440 ?        Ss   21:24   0:00 /usr/sbin/atd
ccuser    4030  0.0  0.1   3392  1036 ?        Ss   21:24   0:00 cc-control [rpc]                                                   
apache    4034  0.0  0.5  31128  5480 ?        S    21:24   0:00 /usr/sbin/httpd
apache    4035  0.0  0.5  31128  5480 ?        S    21:24   0:00 /usr/sbin/httpd
apache    4036  0.0  0.5  31128  5480 ?        S    21:24   0:00 /usr/sbin/httpd
apache    4037  0.0  0.5  31128  5480 ?        S    21:24   0:00 /usr/sbin/httpd
apache    4038  0.0  0.5  31128  5480 ?        S    21:24   0:00 /usr/sbin/httpd
apache    4039  0.0  0.5  31128  5480 ?        S    21:24   0:00 /usr/sbin/httpd
apache    4040  0.0  0.5  31128  5480 ?        S    21:24   0:00 /usr/sbin/httpd
apache    4041  0.0  0.5  31128  5480 ?        S    21:24   0:00 /usr/sbin/httpd
root      4051  0.0  0.0  14368   708 ?        Ss   21:24   0:00 cc-web: master process /usr/local/centovacast/sbin/cc-web
500       4052  0.0  0.1  14520  1324 ?        S    21:24   0:00 cc-web: worker process           
500       4053  0.0  0.0  14368   960 ?        S    21:24   0:00 cc-web: cache manager process     
nobody    4062  0.0  0.0   3408   832 ?        Ss   21:24   0:00 /usr/local/centovacast/sbin/cc-imaged -p 2196 -b 127.0.0.1 -c 50 -i
nobody    4064  0.0  0.0   3468   960 ?        S    21:24   0:00 /usr/local/centovacast/sbin/cc-imaged -p 2196 -b 127.0.0.1 -c 50 -i
nobody    4065  0.0  0.0   3468   664 ?        S    21:24   0:00 /usr/local/centovacast/sbin/cc-imaged -p 2196 -b 127.0.0.1 -c 50 -i
nobody    4066  0.0  0.0   3468   664 ?        S    21:24   0:00 /usr/local/centovacast/sbin/cc-imaged -p 2196 -b 127.0.0.1 -c 50 -i
avahi     4093  0.0  0.1   2708  1304 ?        Ss   21:24   0:00 avahi-daemon: running [SRV-CENTOVACAST.local]
avahi     4094  0.0  0.0   2708   436 ?        Ss   21:24   0:00 avahi-daemon: chroot helper
root      4129  0.0  0.0   3624   416 ?        S    21:24   0:00 /usr/sbin/smartd -q never
root      4133  0.0  0.0   1756   460 tty1     Ss+  21:24   0:00 /sbin/mingetty tty1
root      4134  0.0  0.0   1756   432 tty2     Ss+  21:24   0:00 /sbin/mingetty tty2
root      4135  0.0  0.0   1756   432 tty3     Ss+  21:24   0:00 /sbin/mingetty tty3
root      4136  0.0  0.0   1756   432 tty4     Ss+  21:24   0:00 /sbin/mingetty tty4
root      4137  0.0  0.0   1756   432 tty5     Ss+  21:24   0:00 /sbin/mingetty tty5
root      4140  0.0  0.0   1756   436 tty6     Ss+  21:24   0:00 /sbin/mingetty tty6
root      4150  0.0  1.0  26000 10344 ?        SN   21:25   0:00 /usr/bin/python -tt /usr/sbin/yum-updatesd
root      4152  0.0  0.1   2668  1044 ?        SN   21:25   0:00 /usr/libexec/gam_server
ccuser    4182  0.1  0.5 152540  5696 ?        Sl   21:25   0:00 /usr/local/centovacast/shoutcast2/sc_serv ../lovenight/etc/server.co
ccuser    4198  5.0  0.7 190400  7756 ?        Sl   21:25   0:12 /usr/local/centovacast/sctrans2/sc_trans ../lovenight/etc/source.con
ccuser    4216  0.1  0.1 150320  2032 ?        Sl   21:25   0:00 /usr/local/centovacast/shoutcast2/sc_serv ../sertanejogeral/etc/serv
root      4280  0.1  0.2  10268  2924 ?        Ss   21:28   0:00 sshd: root@pts/0
root      4295  0.0  0.1   4640  1384 pts/0    Ss   21:29   0:00 -bash
root      4320  0.0  0.0   4360   964 pts/0    R+   21:29   0:00 ps aux
[root@SRV-CENTOVACAST ~]#
Title: Re: broadcasters restart all the time and I get several emails saying restarted.
Post by: gutoeterno on January 02, 2013, 03:44:51 pm
And a strange thing happens, I have two radios on this server centovacast v3, but if I start another one does not start at all.
Title: Re: broadcasters restart all the time and I get several emails saying restarted.
Post by: Centova - Steve B. on January 04, 2013, 05:17:46 pm
whilst i find the OP language and attitude abhorrent, i CAN understand their frustration.
I can understand it too, but after that unbelievably rude exchange with DrO after he graciously offered to help, I wasn't about to offer any further assistance to gutoeterno.  But as you've asked...

we have djs that go live every night and as soon as they disconnect and the autoDJ is engaged i start getting the same email every ten minutes telling me that the server has restarted.
That really is quite odd, it could be that either sc_trans2 really is exiting, or that it's still running and Centova Cast just *thinks* it's down.  When this cycle of emails starts happening, is the stream still functional?  Does the audio remain uninterrupted, or does it stop every few minutes and then start up again?

If the audio stops, then check the sc_trans log as I described previously to find out why it's exiting.

The log file can be accessed most easily by just logging into the stream and clicking "Server logs" and then selecting "AutoDJ log" (documented in the manual (http://www.centova.com/doc/cast/user_manual/02_reference_manual/08_Logs)).  If for some reason you want to access it on disk it's /usr/local/centovacast/var/vhosts/USERNAME/var/log/source.log (also documented in the manual (http://www.centova.com/doc/cast/internals/files/accounts)).

If the audio doesn't stop, then something more serious is going wrong and would require further investigation.
Title: Re: broadcasters restart all the time and I get several emails saying restarted.
Post by: gutoeterno on January 05, 2013, 03:55:05 am
Well, the control panel is not the right option Auto DJ LOG, then went straight through and got the server log that User is restarting, but did not understand which part informs the problem. I have attached the log here on this post so that you can analyze.

And as for your question, for the audio completely, but after a few minutes the audio back and get the email that the auto dj was restarted automatically.

I have already installed this build more than 10x and already tested it on CentOS and Debian and all the same problem happens.

I sent an internal message to the data server so that you can better investigate this issue.

You can hear the audio from this server here: http://67.205.104.110:45500/stream

For now thank you for helping me, I'm asking you this helps about 75 days, I'm paying to license this new version and unfortunately I can not ask for any kind of support for the Alexiu already informed me that because it is the only BETA support I can get is from Steve here in the forum, meanwhile keep paying this new power panel without being able to use it.

I count on your understanding.
Title: Re: broadcasters restart all the time and I get several emails saying restarted.
Post by: My Auto DJ on January 05, 2013, 05:19:04 am
Yes it will just happen again, the only solution I have found  is to just disable the mail

http://prntscr.com/o763p
Title: Re: broadcasters restart all the time and I get several emails saying restarted.
Post by: gutoeterno on January 05, 2013, 05:28:32 am
No, but it does nothing AutoDJ because the streaming is falling all the time and coming back.

How will I maintain my business this way?
Title: Re: broadcasters restart all the time and I get several emails saying restarted.
Post by: My Auto DJ on January 05, 2013, 05:37:14 am
LOL it's not easy, I have just been refunding clients the past couple weeks, it was running good but somewhere in a update something went wrong, I have 2 v3 servers one is running great because I have not ran the updates in at least a month but my other installation (the one I have been keeping up with the updates) is running very bad now, have also had mountpoints just disappear for no reason,the disk quota issue is a huge problem and I have no idea what causes it, very frustrating and they tell us "o be patient but this was released in March 2010, they had a v3 countdown clock and everything, 3 years and at least $2K lost in sales and clients, and even worst I'm getting so much v3 traffic and I must turn them down once again :( 
They are right though, this is Beta so we are not really suppose to be selling it but this is what we do --- SELL AUTO DJ's --- at least I got a jump start on my v3 SEO
Title: Re: broadcasters restart all the time and I get several emails saying restarted.
Post by: gutoeterno on January 05, 2013, 05:44:55 am
My AutoDJ Well, after 2 years using this Centova believe I will leave it alone and go to Castcontrol.

Having to pay to license a panel Beta and still not be able to have technical support and just have this forum to seek help will not work anymore. The respsotas here take days for the reply Steve, I know he must be a busy guy completely, but do not understand how this company lets customers Centovacast in hand with this beta without technical support panel and with this forum to get help.

A pity because I always enjoyed this panel Centova, but some customers in Brazil are making a point of using the AutoDJ with Shoutcast V2, and only WHMSonic CONTROLCAST and doing it in a way that does not harm our clients.

I believe I will not find the solution to this problem Centovacast not V3.

Very frustrating all this.
Title: Re: broadcasters restart all the time and I get several emails saying restarted.
Post by: My Auto DJ on January 05, 2013, 05:55:58 am
LOL no you don't want Cast Control, sorry if the Cast Control developer reads this but I have tried that 3 times in the past several years and lost a lot more $$ with that vs anything else, the panel is very hard for clients to understand... rather than give clients refunds I got PayPal disputes and chargebacks, no nothing beats Centova Cast period just use the v2 version I have servers running v2 for years non-stop with zero issues.
Title: Re: broadcasters restart all the time and I get several emails saying restarted.
Post by: gutoeterno on January 05, 2013, 06:28:47 am
But you have the centovacast v3 running shoutcast v2?

If you like you did to install?
Installed on which Linux distribution?
What packages installed before you install the new Centova?
Title: Re: broadcasters restart all the time and I get several emails saying restarted.
Post by: My Auto DJ on January 05, 2013, 06:47:02 am
Sorry, don't understand, this may help though
http://www.hark.com/clips/zwdhthcxhb-dont-speak-freaky-deaky-dutch
Title: Re: broadcasters restart all the time and I get several emails saying restarted.
Post by: gutoeterno on January 05, 2013, 07:03:26 am
?????????????
Title: Re: broadcasters restart all the time and I get several emails saying restarted.
Post by: gutoeterno on January 05, 2013, 07:12:08 am
I do not understand for what reason I sent this site.

I'm formatting the server again and now I'm trying to install CentOS Centovacast V3 in 6.3 and will install all these packages before:

http://www.howtoforge.com/installing-apache2-with-php5-and-mysql-support-on-centos-6.3-lamp

Only then will install Centovacast V3

For in all my installations I had done what I did on CentOS 5.8

I do not know if I'm wasting my time again but as I have no other outlet and not seek support where I have to go trying in many ways.

Thanks My Auto DJ!
Title: Re: broadcasters restart all the time and I get several emails saying restarted.
Post by: gutoeterno on January 05, 2013, 07:48:33 am
Ok, install:

Linux CentOS 6.3
Apache 2
Mysql
phpmyadmin

continue.......
Title: Re: broadcasters restart all the time and I get several emails saying restarted.
Post by: gutoeterno on January 05, 2013, 07:51:51 am
I'am run the command:

./install.sh --channel=unstable --shoutcast2 --sctrans2

continue.....
Title: Re: broadcasters restart all the time and I get several emails saying restarted.
Post by: gutoeterno on January 05, 2013, 07:57:08 am
Ok, ok .. perfect installation.
Let the creation of Webradio ....

continue...........
Title: Re: broadcasters restart all the time and I get several emails saying restarted.
Post by: gutoeterno on January 05, 2013, 08:29:08 am
It seems even slutty ....
All right, but now a problem that ever happened to me.

I created the radio, mounted the playlists and climbed the MP3.

But when I mount the MP3 playlists to guess?

Shows no basis in MP3 .... joke ...
Title: Re: broadcasters restart all the time and I get several emails saying restarted.
Post by: Centova - Steve B. on January 08, 2013, 09:26:25 pm
gutoeterno, I'm afraid I can't understand about 75% of what you're saying here on the forums, which makes it rather difficult to assist you.  In particular your comment about something seeming "slutty" appears to be a pretty awful mistranslation. ;)

With that said, looking at your sc_trans2 log, your problem *appears* to be either in DNAS2 or in sc_trans2 (and does NOT appear to be Centova Cast-related), based on the following entries:

Code: [Select]
2013-01-05 09:25:27 E msg:[UVOX2] 1529518295 [UVOX2] 1529518295 socket send error.
2013-01-05 09:25:27 E msg:[UVOX2] 1529518295 Waiting 30 seconds
2013-01-05 09:25:53 I msg:[UVOX2] 1529518295 Creating stream socket
2013-01-05 09:25:53 I msg:[UVOX2] 1529518295 Connecting to stream host
2013-01-05 09:25:53 W msg:[UVOX2] 1529518295 Error connecting to stream host [waiting 30s]
2013-01-05 09:26:19 I msg:[UVOX2] 1529518295 Connecting to stream host
2013-01-05 09:26:19 W msg:[UVOX2] 1529518295 Error connecting to stream host [waiting 30s]
2013-01-05 09:26:45 I msg:[UVOX2] 1529518295 Connecting to stream host
2013-01-05 09:26:45 W msg:[UVOX2] 1529518295 Error connecting to stream host [waiting 30s]
2013-01-05 09:27:11 I msg:[UVOX2] 1529518295 Connecting to stream host
2013-01-05 09:27:11 W msg:[UVOX2] 1529518295 Error connecting to stream host [waiting 30s]
2013-01-05 09:27:37 I msg:[UVOX2] 1529518295 Connecting to stream host
2013-01-05 09:27:37 W msg:[UVOX2] 1529518295 Error connecting to stream host [waiting 30s]
2013-01-05 09:28:03 I msg:[UVOX2] 1529518295 Connecting to stream host
2013-01-05 09:28:03 W msg:[UVOX2] 1529518295 Error connecting to stream host [waiting 30s]
2013-01-05 09:28:29 I msg:[UVOX2] 1529518295 Connecting to stream host
2013-01-05 09:28:29 W msg:[UVOX2] 1529518295 Error connecting to stream host [waiting 30s]
2013-01-05 09:28:55 I msg:[UVOX2] 1529518295 Connecting to stream host
2013-01-05 09:28:55 W msg:[UVOX2] 1529518295 Error connecting to stream host [waiting 30s]
2013-01-05 09:29:21 I msg:[UVOX2] 1529518295 Connecting to stream host
2013-01-05 09:29:21 W msg:[UVOX2] 1529518295 Error connecting to stream host [waiting 30s]
2013-01-05 09:29:47 I msg:[UVOX2] 1529518295 Connecting to stream host
2013-01-05 09:29:47 W msg:[UVOX2] 1529518295 Error connecting to stream host [waiting 30s]

sc_trans2 is experiencing a socket error while sending data to DNAS2.  You'd want to check your DNAS2 logs for the same date/time to see what DNAS2 has to say about it.

If this is indeed a problem with the SHOUTcast toolset, the best person to help you diagnose this would be the current developer of the SHOUTcast toolset, DrO... so it's rather unfortunate that you basically flipped him off when he tried to help you previously in an earlier post in this thread.
Title: Re: broadcasters restart all the time and I get several emails saying restarted.
Post by: gutoeterno on January 09, 2013, 03:38:56 am
Steve, firstly thank you for responding.

Secondly, this User DRO made ​​an unfortunate comment and it did nothing for my problem and some users of Centovacast v3.

I'm two months trying to solve this problem by testing different versions of what is possible and so far nothing to solve the problem.

All of us here pay monthly for the license to use, test, improve new product Centovacast, exactly for this reason I think the company Centovacast Inc. should give priority to our problems and not be dependent on its User who made an unfortunate comment, because the only thing that appeared to be DRO is a person who finds himself above anyone else, but he is nothing more than a being like all of us here.

I believe that we consumers of the product is that we are "gods" here because we pay and we use Centovacast and us is that we do what other companies in the industry can not reach a global market that is only growing in this segment and all points check that the Centovacast Inc. achieve a more global mercaod is

You to understand and everyone reading this go to that post and see for yourself if I mistreated this User DRO, it did not help and neither contributed nothing, in short, he missed a great chance to remain silent.

Thanks and matter closed.
Title: Re: broadcasters restart all the time and I get several emails saying restarted.
Post by: DrO on January 09, 2013, 04:58:50 am
and as i stated at the time, i have no direct knowledge of what and where Centova handles sc_trans or any of the SHOUTcast tools (seeing as i don't have a copy or the means to access a working setup).

i don't get what your superiority complex is all about from the tone of your posts. i was not being 'above anyone else'. but yes i did make a mistake, trying to respond to you in the first place (i don't know if it was an inability to understand my english or that is just how you are) but i was clear in that i don't know Centova's workings and gave the best suggestion i could on what to try to look for - so i didn't get the name of the file correct but looking back, there was enough information in the log output for someone with access to the machine to look in the folders being shown so you could then try to figure out the actual log file.


what is needed is a test build of sc_trans to try to determine if the fixes which have been made internally make any difference or not. however, i cannot just provide a test build and say to install it when i've made default changes to the sc_trans behaviour to resolve port binding issues and other things. so it would typically require someone from Centova to first test that things will work and then it can be tried out.


but now twice you've basically told me to f**k off, yet you demand a solution from Centova when that is unlikely the point of the issue based on everything else i've been reading from the other threads and posts about this issue.

so what do you want? me to provide Centova with a test build of sc_trans to then see if that works or for me to f**k off and you then keep complaining that no one is helping you and blaming Centova when it is not their issue?

the ball is in your court!
Title: Re: broadcasters restart all the time and I get several emails saying restarted.
Post by: gutoeterno on January 09, 2013, 06:03:10 am
Hello DRO

It's really a pleasure to talk to you and know that we can help with all of the new users here Centovacast v3

Thanks indeed to collaborate, we know that there is no obligation to help, but their help is worth gold to us, I know how to pay a monthly license for Centovacast Inc. that she should instead have an obligation to help us, but it is a BETA they do not give any official support, but you must pay them a monthly license this BETA version, good is not going to understand?

I have a test server in the air and that is giving this error, I tried to install it several times and used numerous versions and the error persists.

I have another test server with Centovacast v3 but he is running Shoutcast v1 and works perfectly fine, so the problem is even Shoutcast v2

I'll send you a message with offline data from the server and you can see what really happens on the server.

When you see the problem happening and when you find the problem, please post the solution here so that other users of the Forum can also solve their problems.

Thanks again Dro.
Title: Re: broadcasters restart all the time and I get several emails saying restarted.
Post by: Centova - Steve B. on January 09, 2013, 11:55:41 am
All of us here pay monthly for the license to use, test, improve new product Centovacast, exactly for this reason I think the company Centovacast Inc. should give priority to our problems and not be dependent on its User who made an unfortunate comment
While I appreciate the difficulty of your situation, I feel it's important to clarify that you're paying monthly for a license for Centova Cast v2, and we give full, priority support to v2 issues via our helpdesk.

It just happens that we've designed v3 to accept the same licenses.  You're *choosing* to use your license with an unstable beta product, knowing full-well in advance that the only support we provide for it is via the forums where I periodically check in, and other community members assist.

Also FYI, you absolutely DO NOT have to pay to test v3.  We bumped our trial licenses up to 30 days (from 14) specifically for this reason when the first build of  v3 was released, and you're welcome to order as many trials licenses as you need to test v3.

because the only thing that appeared to be DRO is a person who finds himself above anyone else, but he is nothing more than a being like all of us here.
Maybe I haven't been clear enough about this, but no, he is not "like all of us here".  DrO is the current developer of the SHOUTcast toolset (sc_trans2 and SHOUTcast DNAS 2), so his knowledge of those products goes far above and beyond anyone else here, including me personally.

While he did not know the specific filename that Centova Cast configures sc_trans2 to use for its log file (because that's specific to Centova Cast) he is effectively the authoritative reference on all things SHOUTcast-related, and we're damned lucky to have him volunteering his time here on our forums.

I believe that we consumers of the product is that we are "gods" here because we pay and we use Centovacast and us is that we do what other companies in the industry can not reach a global market that is only growing in this segment and all points check that the Centovacast Inc. achieve a more global mercaod is
It's no secret that our clients are everything; without our loyal clients, we'd have no business at all and we'd be stuck in a different line of work altogether.  And when it comes to v2, I do hope our clients feel that appreciation in their dealings with us.

With that said, we have explicitly and repeatedly told our clients that Centova Cast v3 is a preview only and is not yet ready for production use, yet you and others are doing so and then complaining loudly when it doesn't yet work in production.  With all due respect, if I hand you a hammer and say "don't hit yourself in the forehead with this", and then you promptly use it to crack open your skull... well, you get the idea. ;)

Further, this issue is not looking like a Centova Cast issue at all (although again, I'd need you to do what I asked in my previous message in order to test that theory) so the whole discussion surrounding the level of support for this issue may be moot -- if it's a sc_trans2 issue, there's nothing we can do to resolve it on our end anyway.
Title: Re: broadcasters restart all the time and I get several emails saying restarted.
Post by: gutoeterno on January 09, 2013, 12:22:27 pm
Ok Steve, wise words and beautiful words.

But let's focus on the problem of users.
If the problem is in sc_trans2 how to solve?

The Centovacast Inc. will release the new version with the problem of resumption AutoDJ??

Help me understand this, because from what you told me is saying that he can do nothing, then this panel may not be sold, I really did not understand at what point you want to reach.

I already sent you the data ssh on my test server gently, so that you can see with your own eyes and this problem can finally give us the help we both dreamed.
Title: Re: broadcasters restart all the time and I get several emails saying restarted.
Post by: Centova - Steve B. on January 09, 2013, 12:41:11 pm
But let's focus on the problem of users.
If the problem is in sc_trans2 how to solve?
Per the last paragraph of my last message (and as mentioned in several prior messages) if this is in fact an sc_trans2 issue there is absolutely nothing we at Centova Technologies can do about it because sc_trans2 is not our product.  sc_trans2 is owned by AOL/Nullsoft and we are not affiliated with them in any way.  You would just have to wait for a fix from them.

The Centovacast Inc. will release the new version with the problem of resumption AutoDJ??
Sorry but I don't think you've understood what I've said in my last few messages.  If it's an sc_trans2 issue, there is nothing we could do to fix it in a new version because again, sc_trans2 is not our product and any bugs in sc_trans2 are unrelated to Centova Cast.

sc_trans2 is owned and developed by AOL/Nullsoft.  DrO is the guy who maintains the sc_trans2 code there -- he does not work for us.  We at Centova Technologies have NOTHING to do with sc_trans2 development.

Help me understand this, because from what you told me is saying that he can do nothing, then this panel may not be sold, I really did not understand at what point you want to reach.
If this is an sc_trans2 issue it has nothing to do with Centova Cast or the sale of v3.  If it's an sc_trans2 bug,  then it's not specific to Centova Cast, and anyone who is using ANY stream control panel (or no control panel at all) will encounter this same issue with sc_trans2 if their configuration triggers the same bug.

Again though, we still don't know if it's an sc_trans2 issue or not.  I've asked you in message after message to check your DNAS2 logs to help confirm this, and that's the only way we can know for sure.
Title: Re: broadcasters restart all the time and I get several emails saying restarted.
Post by: gutoeterno on January 09, 2013, 01:01:58 pm
Correct, then we expect the users we would appreciate the help of the User Dro.
Now the ball is in time with him.

As I said before, I already sent you the data from my test server offline for a message so you could kindly look and see the problem and know who's to blame, or NullSoft or Centova.

The fact is that we are users, and for being users, we lay, dumb, stupid sometimes not aware in as deep as you and User Dro.

I believe that this problem could have been solved already passed the days and here if you conectase Forum on the server and look for you own where the problem lies.

I have kindly granted him access via ssh from my server so that you can see the problem.

Remembering that I'm here at the Forum to contribute and make critical, but constructive criticism, so you might as Administrator increasingly improve their product.

Just this.
Title: Re: broadcasters restart all the time and I get several emails saying restarted.
Post by: sleeper on April 08, 2013, 09:44:04 am
Although I must say that gutoeterno has not responded with any type of professionalism at times on this post, frustrated people do tend to be rude. After all if the customer was happy they wouldn't be having issues to post about.

DrO although I see you were trying to be helpful in the original post, posting that you have no idea how to help and hes already been told what to do after he said he couldn't find the file isn't a very productive post and I can understand how that can be frustrating to someone who is looking for help. Sometimes its best to only post when you can actually help the matter.

And Steve B.to say that you decided not to help because you didn't like his attitude is definitely not a professional response. If I didn't help all the customers I don't like based on their attitude I wouldn't have to do much work..lol

All this being said however I've noticed the main response to this post is simple "your using a beta program and things don't work right all the time in beta testing" Yet I am having the same issue now and according to Centova the V3 is no longer in beta testing. I choose not to bother with the program and to stick with V2 till the official release of V3 to avoid issues just like this. For 10 hours I received a copy of this email every 10 mins. And although I haven't heard from the client yet I am pretty sure that after he sees 150 emails in his inbox telling him that his server restarted I'm sure hell be calling. So I searched to see how to resolve this issue before he brought it up to me. And seeing the contents of this post is not a promising start.

I have checked the error logs with no noticeable reason to tie to this showing up (the AutoDJ log seems to have no time stamp this seems useless when trying to match up to the times you were having errors) The Error log showed nothing before the ending of the emails.

So if we can not seem to sort out why, is there at least a way to turn of this specific email from being sent out 150 times to the client? I would think that we should have the ability to pick and choose what emails we want to be used. Not having the option to disable an auto email seems a bit odd to me.

In final this is no longer being beta tested, so is there a resolution to this issue yet?
Title: Re: broadcasters restart all the time and I get several emails saying restarted.
Post by: Reinaldo C. Andrade on April 08, 2013, 05:38:55 pm
Friends, I have this problem, from the time that I installed  ccV3 in my server.
Steve says is a problem with Sc_trans_V2, unsolved momentarily, until the Nullsoft do an update with the fix for this problem.
Another problem is the quality of audio in AACP performed in live broadcasts using DJport.
This quality has never been or will be met as AACP.
Anyway, I gave up trying to in solve the problem and I'm using only shoutcastV1 and Icecast2 in my seasons, until such problems are resolved by Nullsoft.
If you have another solution, I am buying and paying well.
Title: Re: broadcasters restart all the time and I get several emails saying restarted.
Post by: Centova - Steve B. on April 09, 2013, 09:56:41 pm
Although I must say that gutoeterno has not responded with any type of professionalism at times on this post, frustrated people do tend to be rude. After all if the customer was happy they wouldn't be having issues to post about.
You realize this is a 3 month old thread, right? ;)

DrO although I see you were trying to be helpful in the original post
DrO will never see your reply, unfortunately, as after the barrage of nasty posts he received in response to simply trying to help, he stopped visiting our forums.  Which is a big loss to everyone else here who actually appreciated the free support he was trying to provide in his free time.

And Steve B.to say that you decided not to help because you didn't like his attitude is definitely not a professional response. If I didn't help all the customers I don't like based on their attitude I wouldn't have to do much work..lol
That's not quite what I said.  The forums are a venue for people to provide voluntary assistance to other members of the community.  They're not part of our official support offering, and I don't respond to every thread here.  Had this been a helpdesk ticket (eg: paid support), it would have been a different situation -- although even on the helpdesk, there are limits to the amount of abuse I'm willing to allow my staff to be subjected to.  But here on the forums, I'm not going to continue volunteering my time in participating in a forum thread where people are getting abusive.

All this being said however I've noticed the main response to this post is simple "your using a beta program and things don't work right all the time in beta testing" Yet I am having the same issue now and according to Centova the V3 is no longer in beta testing.
Centova Cast v3 is no longer in beta, but SHOUTcast DNAS v2 and sc_trans2 are both still beta products.  If you choose to use them with Centova Cast, you do so at your own risk.  We do not and cannot guarantee that they will work for you as they are third-party products that are totally outside of our control.

We will guarantee OUR side of the relationship, of course -- if there are any bugs in our DNAS2/sc_trans2 integration, we will most definitely fix them as they are reported -- but ANY SHOUTcast control panel vendor who claims to be able to guarantee the stability of DNAS2/sc_trans2 is lying to you to make a sale.  Only AOL/Nullsoft can control the stability of their software.

For 10 hours I received a copy of this email every 10 mins.
That's not related to this thread; that sounds like your configuration has been trashed or somesuch.  This thread is about an intermittent crash in sc_trans2.  If you're getting the emails consistently every 10 minutes, that means your sc_trans2 is consistently exiting after a short period of time, every time Centova Cast restarts it, which is a very different situation.

I have checked the error logs with no noticeable reason to tie to this showing up (the AutoDJ log seems to have no time stamp this seems useless when trying to match up to the times you were having errors)
And the above sounds like you're talking about ices, not sc_trans2.  If so, you're completely in the wrong thread -- this thread is specifically in regard to sc_trans2.  (And agreed, I think it's silly that ices does not log timestamps.)

So if we can not seem to sort out why, is there at least a way to turn of this specific email from being sent out 150 times to the client?
Sure can.  Would be much easier to help you if you opened a helpdesk ticket though.

I would think that we should have the ability to pick and choose what emails we want to be used. Not having the option to disable an auto email seems a bit odd to me.
Sure would be odd.

In final this is no longer being beta tested, so is there a resolution to this issue yet?
To your issue, which has nothing to do with this thread?  Probably -- in fact, almost certainly.  To the issue with sc_trans2 which is the topic of this thread?  No, that can only be resolved by AOL/Nullsoft.
Title: Re: broadcasters restart all the time and I get several emails saying restarted.
Post by: sleeper on April 10, 2013, 08:19:26 am
Wow Steve thats a lot to take in there...lol

1) I did realize its a 3 month old thread. I posted on this thread as I saw someone having issues with the emails and the stream restarting. I wasn't sure if it was specific to one autodj setting or to centovacast in general.

2) DrO is a grate help so its definitely a downer if hes chosen not to help here anymore. Unfortunately dealing with people on a forum can be quite annoying. On both sides at times.

3) If you noticed the "lol" after my comment about your response you would of hopefully noticed it was meant more jokingly. I understand how forums work.

4) I am dealing with icescc in this mater and not the DNAS2

5) Being sarcastic about the topic of the thread vrs the issue I was dealing with gave me a good laugh this am. I'm sure your used to dealing with a lot of a-holes on this forum I however am a very sarcastic down to earth person so I take no offense and enjoy the humor. Although if I had to deal with the same people you do everyday I might not feel the same about that.

6) as for the "Sure would be odd." comment am I missing something? The system sends out email and I don't seem to see an option to disable or enable specific emails.

And lastly I don't think at this time I'll need to open a ticket now, after running an update as we talked about in another post to fix another issue this issue hasn't repeated itself.
Title: Re: broadcasters restart all the time and I get several emails saying restarted.
Post by: Reinaldo C. Andrade on April 10, 2013, 01:25:44 pm
Friends, I do not want to participate in this discussion who said this or that, but in my opinion, who should collect the solution at Nullsoft, should be Centova Tecnology and not us, simple users.
Steve, would be of great help if you would focus their efforts in collecting a solution to the problem of Nullsoft and let us know what they say.
The Nullsoft should be working for a solution, I believe it, but we need to know: When will there be an update to fix this? If not, we'll be here waiting ... waiting ... and frustrated, wondering if there really a solution in the short or long term.
For, as is, ccV3, offers no novelty (against ccV2) because the main innovations depend on the proper functioning of  Sc_trans_2.
Food for thought: Imagine you buy a car from an automaker that uses the engine from another manufacturer and assembler of whom you bought the car, do not take responsibility of an engine problem.
Title: Re: broadcasters restart all the time and I get several emails saying restarted.
Post by: Centova - Steve B. on April 19, 2013, 08:46:19 pm
Steve, would be of great help if you would focus their efforts in collecting a solution to the problem of Nullsoft and let us know what they say.
I/we have absolutely no pull with AOL's management, and DrO is already aware of this issue.  He is only able to invest time in it as his management permits, and has indicated that they're not interested in investing much time into it at the moment.  I truly hope he gets time to work on it in the near future.

Food for thought: Imagine you buy a car from an automaker that uses the engine from another manufacturer and assembler of whom you bought the car, do not take responsibility of an engine problem.
The big difference there is that when you buy a car, you're paying the automaker for the engine.  The engine isn't a free add-on, and you can't replace the engine with other alternatives as you see fit.

When you buy a Centova Cast license, you're paying for a Centova Cast license.  You're not paying us for DNAS2 or sctrans2.  And unlike an automobile engine, you are not required to use DNAS2 or sctrans2 -- you also have the option of using DNAS1, IceCast, etc.

So really, a better analogy would be: Imagine you buy a car from an automaker.  And the street you live on has potholes in it.  Your car can drive on other streets, but you want to drive on yours.  Do you contact the automaker and ask them to deal with the potholes?  Or do you contact the city?  Or do you just drive on a different road with no potholes?

Further food for thought: Nobody pays taxes in your city/country, so nobody is being paid to upkeep the roads.  The city is willing to fix the roads voluntarily, but because nobody's paying for it, they can't offer a time frame.  Is that the automaker's fault? ;)
Title: Re: broadcasters restart all the time and I get several emails saying restarted.
Post by: J.J. Draijer on April 30, 2013, 04:04:41 am
Steve,

The comparising with the car is in my opinion not very relevant  ;)

You state, we pay for a Centovacast license, which is offcourse true. But i think the most of the users select Centovacast because of the functions it contains, for example the DJ logins etc. These functions ONLY work with Shoutcast V2 and not with V1. So basicly we all pay for half a product if we need to use V1 or Icecast. So why we need upgrading then you would think :)

We do not select a car based on an engine (although some do), but more on brand and stability. If an engine cannot work with 5 gears, and the car provides it, you can't say: then only  use 4 gears, then it runs fine.  I sure understand what you mean, but i believe it does not add up :)

We also suffer problems with crashing streams with SC_TRANS and indeed it is costing customers.
But they select the streams based on the functions. Without these functions, CC is basicly just an update on the layout (and the engine). All other functions do not work (properly)  :( And that is sadly.

Offcourse i know, it is not your product, but some more information/actions from NullSoft would be great. Maybe we can do this collective ?

To be clear: we have an outstanding support ticket about this issue, so we can try to find out the cause of this problem. And i'm more then willing to help you guys finding the issue, as i cannot find it myself.