WeatherStar 4000

Playground
,
#87

So every now and then my ws4channels container will get hung up and will display the following error messages in the log:

(node:1) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 SIGINT listeners added to [process]. Use emitter.setMaxListeners() to increase limit
(Use node --trace-warnings ... to show where the warning was created)
(node:1) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 SIGTERM listeners added to [process]. Use emitter.setMaxListeners() to increase limit
(node:1) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 exit listeners added to [process]. Use emitter.setMaxListeners() to increase limit
(node:1) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 SIGHUP listeners added to [process]. Use emitter.setMaxListeners() to increase limit

A simple restart of the container fixes this and everything is back to normal. I have my ubuntu server set to automatically reboot at 2am every night, so sometimes when everything boots back up, the ws4channels container will start with the above errors. I have another container that automatically restarts ws4channels at a certain time, but I've since come to notice that even after a restart from that sometimes, these errors still occur. Any idea what might be causing this and what to do to fix it?

#88

Since I know you're already running the docker version of cc4c, I'm curious why you're running this project as well? Given you can setup ws4kp as a virtual channel using cc4c (which only runs when tuned to), it seems like a waste of system resources to run both (I believe @rice would agree with this).

#89

Good point…didn’t even think I could just use cc4c with ws4kp. Although, won’t the dimensions of the display that loads be way off then? I thought that was the purpose of ws4channels to properly create a window that will load with a good look in channels?

#90

More details a few posts up:

1 Like
#91

Ok…I’ll have to give these instructions a try then. Thanks!

#92

Since I’m running Ubuntu Server, everything is headless for me. I will never see an actual chrome window open on a desktop GUI. Am I still able to do this through CC4C then because you mention removing those kiosk parts and hitting enter and then putting them back in and hitting enter…but of course I’m never seeing an actual chrome window open. I do have a ton of environment variables already specified in the stack compose so maybe that bypasses the whole need to remove part of the link and hit enter? But then is there an env variable you can put in to have it always start with the music playing?

#93

As described in the linked post, you need to temporarily connect to the container using a VNC client to allow you to interact with Chrome running in the container.

This is true for any needed interaction with the container's Chrome instance. For example, if you need to enter credentials to login to a streaming website. This is an important concept to have a grasp on when you're using the Docker version of cc4c.

#94

I do agree, the only reason to run ws4channels is if you desire to have an instantly loading channel and are willing to take the small resource hit since it runs all the time.

@Accustiver I pushed a new latest to try a fix for the issue you’re having. Give it a try if you like. I haven’t tested it as I don’t run the latest ws4kp 6.0+ that uses the different crop.

1 Like
#95

Pulled your latest version of ws4channels and it seems to be doing fine even after a few restarts of the Ubuntu Server. And looking at stats of my system, this certainly doesn't seem to be taxing things too much. So for now I think I'll continue to use the ws4channels container over the cc4c method as that option seems to be a little more involved with my particular setup. Thanks again!

#96

I’m sure it is user error, but I’m getting a “192.168.7.180:8080 already in use” error, with 192.168.7.180:8080 being what I input for my Channels DVR. If it matters, I did try installing this once previously, and got the package not found error that another user reported, so maybe some remnants are around on my server? But nothing shows up in Portainer.

Standard output:


192.168.7.180:8080 already in use

Standard error:


+ dvr=192.168.7.180:8089  
    ++ basename /config/weatherstar4k.sh  
    + extension=weatherstar4k.sh  
    + extension=weatherstar4k  
    + cp /config/weatherstar4k.env /tmp  
    + envFile=/tmp/weatherstar4k.env  
    + [[ -n 192.168.7.180 ]]  
    + extensionURL=192.168.7.180:8080  
    + [[ # == \# ]]  
    + cdvrStartingChannel=  
    + [[ -n '' ]]  
    + cdvrIgnoreM3UNumbers=  
    + curl -s -o /dev/null http://192.168.7.180:8080  
    + echo '192.168.7.180:8080 already in use'  
    + exit 0
#97

OK, so your CDVR server is running at 192.168.7.180:8089 correct?

And, you want the ws4kp container (which is what's spun-up by this weatherstar4kp stack), to run on port 8080? Project One-Click confirms that port is available, and apparently on your system it is not. It's the same for me, so I entered 8090 as the port I want to use for this stack.

The other thing you need to provide correctly is the IP or hostname of the system running cc4c, along with the port. For me, that value is cc4c:5589, for you it's maybe 192.168.7.180:5589?

#98

Ah, thanks. Changing the port from 8080 to 8090 did it. I didn’t realize I had something else running there, but with all the projects going that I’ve been enjoying, it is probably one of them.

#99

Could be halverneus static-file-server that's part of OliveTin for Channels.
Unless you changed it, the default port is 8080.
Compose

services:
  static-file-server:
    ports:
      - ${HOST_SFS_PORT:-0}:8080

Environment variables

HOST_SFS_PORT=8080
#100

Now all I get is the WeatherStar placeholder, with no actual data. I scanned this thread, but I'm not sure where to go from here.

CleanShot 2025-09-21 at 14.14.02@2x
CleanShot 2025-09-21 at 14.14.02@2x2898×1844 244 KB

#101

Described here:

Even though you're not running the container version of cc4c, you still need to follow the couple of steps described in Chrome.

#102

Thanks. Clearly my scanning the thread was careful enough. For anybody else doing this, make also sure that you follow the instructions on the machine you're actually running this on. I did it in a browser on another machine, using the address where it was hosted, and that only made the changes visible on that machine.

#103

I've been having the restart issue pop back up again occasionally where after rebooting my linux server, the ws4channels container doesn't properly load. A simple restart of the container seems to fix it. This hasn't been happening as much as what it used to be prior to the latest fix you did a month ago, but it's still been happening every now and then over the last couple weeks. Here is what I'm seeing in the logs:

(node:1) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 SIGINT listeners added to [process]. Use emitter.setMaxListeners() to increase limit
(Use node --trace-warnings ... to show where the warning was created)
(node:1) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 SIGTERM listeners added to [process]. Use emitter.setMaxListeners() to increase limit
(node:1) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 exit listeners added to [process]. Use emitter.setMaxListeners() to increase limit
(node:1) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 SIGHUP listeners added to [process]. Use emitter.setMaxListeners() to increase limit

Not sure if some further tweaks can prevent this from happening for good? Thanks as always for the help!

#104

I’ll try to check it out sometime later this week.

1 Like
#105

Made some tweeks to hopefully fix maxlisteners. Use the Latest tag. Also some people using this wanted custom channel number in environments with a default of 275. This is not needed for channels but they are using other software. This changes some of the unique channel ids so be aware that you may need to choose your own channel number in the channels source and reload the source in channels and possibly run a delete and recreate guide database. It might not be an issue at all though. Let me know if there are any issues as I can’t test it because I run an older ws4kp.

#106

Updated it and everything seems to be working fine so far after a few restarts. Fingers crossed…thanks!

1 Like