Ghostcast Server Portable
Eliora Shopbell
We have created several jobs, that run without issue. But we have a job that runs, which seems to be an older version of one of our job (it gives wrong results, and is run twice). We can detect it as it sends email, but I can't find any trace of it in Jira. I have looked in the logs using the the "view server log files" script.
We have an Asterisk server hosted externally. On four locations we've gotten ghost calls. These are calls with different numbers like 1000, 9999 or 6060. We don't use these numbers, not even that range.
As you stated this is an issue with home/remote users primarily it is most likely they you would see two things.1- This SIP invite they receives has nothing to do with you Asterisk server. I've seen the source IP be an unknown server, as well as the users own home public IP.2- If the user picks up they will report hearing dead air.
I failed to bookmark a blog post I found where they posted several IPs of SIP scanners they found. However most home users do not have a network capable of blacklisting the IPs from list. If you do not have some fail2ban system on you asterisk server you should add that. You should also make sure your SIP credentials do not include the ISDN number of the user.
Is it some harmeless process that connects to this phone and causes the phone to think a call is made?Usually this is more annoying then harmful. If you find the same thing happening on your Asterisk server you need to harden your server. A invite to a end user device would be harder to find a way to bill the user for service, although there has to be some reason why someone is spanning for these services to begin with.
If this issue is only at the home location, I would look at what is the difference between your office location and the home locations. I think it would be ghost calls at the office location and home locations if there is something with the asterisk server/internet connection for it.
If you have a sip client/server connected with a public ip on port 5060 you will get a lot of connection attempts/ghost calls from people trying to use your credit to route their SIP calls (we had a customer experience this, he's asterisk got used by a phone company and they routed phone calls to cuba during some hours during a weekend and that customers lost until he's account was shut down. He lost around $50k)
The process stops just fine, the problem is the new process launched by the script doesn't run in the same terminal. System monitor indicated the process running, and sure enaugh you can join the server just fine. The problem occurs when I want to use the server terminal, as it is nowhere to be found. Using screen doesn't help either, the screen session stops where the original java stopped, yet the process starts to live somewhere else.
As far as I know, Minecraft servers have a log folder under which you can find the console output duplicated in real time, so this should not need a separate option on screen (it exists, but having two similar log files doesn't seem to be what you aim to achieve).
This is a script I use to get the server going for the first time after launch. It executes the java -Xmx14336M -Xms14336M -jar paper-1.18.1-108.jar nogui command inside a new screen called 'minecraft', then detaches from said screen. If you use screen -r minecraft you'll be able to see and interact with the console.
This is the restarting script itself, all comments inside it explain pretty well what each line does. All in all you'll see the server stop, when it is done closing the screen session will close (sometimes these sessions become 'dead' this is what the last screen -wipe line is for). After 10 seconds, a new screen session with the same name (but most likely a different PID) will be launched with the same parameters.
After applying the arguments, you must restart server, and then you need to visit every grid (by ghost cmd or fly cmd) and use "cheat DestroyWildDinos" to remove already spawned damned from the server. This will kill animals too, but they respawn quite fast.
to my server. Restarted everything. Did a destroywilddinos in logged in as admin. Watched the fleet of the Damned explode then spawn right back in. I tried 0.1, 0.01 and 0.001. No change. They are just as bad a cockroaches.
You added those values in the GridEditor, exported and overwrote the existing ones? Then restarted and did the admin command?
It works on my server. I have 6 grids, Sailed a lot today, only saw 1 damned during a 4 hour session
Very strange. Then I'm out of options. It works fine on my server, and a lot of other people have it working fine too.
That is at least the config that is needed to reduce the spawn rate of the damned.
I'm not a Ghost or Linux expert, but after some more back and forth with DO support, we narrowed it down to a problem with how the requirements for running Ghost's matched against the server defaults. I have some thoughts on what was going wrong (see the end notes on caching), but given that most people are more interested in getting their sites back up and prevent them from going down again, I'll jump straight into the solution.
There are two options you can pursue here. I'll use an aviation metaphor to describe them: assume you're trying to land a plane that's lost control. The first option is to build more runway, aka to upgrade your server to a configuration with higher RAM, higher Memory, etc. This will obviously increase your flat monthly costs, but it means your server has more raw space to deal with what you/Ghost throw at it.
Specifically, you need to build a memory swap on your server. A memory swap guards against out-of-memory errors by allocating hard drive space for temporary memory space when your temporary memory needs outgrow what your RAM can handle. It's not efficient - RAM space is designed differently from SSD (hard drive) space - but it helps with the whole not-bringing-down-the-server problem. And, given that hard drive space is cheaper than RAM (even the lowest Digital Ocean droplet starts with 25gb of hard drive space but only 1gb of RAM), this is a cost effective way for you to solve this problem.
Not only that, but I quite stupidly misconfigured my newsletter sign-up form and so I started to see a lot of errors being hit on the server as people tried repeatedly to submit information but failed (I only realized this later in the evening).
Murmur is running on Mac OS and has been working fine for over a year now. I came back from a three week vacation and whenever someone is connected they will get be shortly (but not instantly 30 secs) disconnected. In the server log it says "disconnecting ghost".
I have completely deleted and reinstalled all the mumble server files. So the current server is a completely fresh version downloaded from the site. I have also updated my client to the most recent version.
The server was falling asleep. When the server went into sleep mode it probably closed some network connections which prevented murmur from receiving packets from users. The murmur server would then consider that user a ghost and disconnect them.
By deploying outlet-metered intelligent rack PDUs and Data Center Infrastructure Management (DCIM) software, you can quickly spot ghost servers and decommission them to free up valuable cabinet space that would be better utilized by more useful equipment.
In an easy-to-understand dashboard chart, you can see the power load of all your servers. This provides an at-a-glance view of which servers have stopped drawing power and can be eliminated or redeployed elsewhere.
582128177f