tstamphaus Posted June 29, 2020 Posted June 29, 2020 Hi all, I just noticed that my account is suspended. I don't know why. It's regarding the followin account:a. your HelioHost username: tstampb. the server your account is on: tommyc. your HelioHost main domain: tstamphaus (and subdomains www.stamphaus.nl and recently added www.cj7limited.nl) Main site (www.stamphaus.nl) is already up and running for a long time. I'm building a second site (www.cj7limited.nl) currently so I guess it has something to do with that. Started with wordpress but yesterday I noticed your strong advice not to use Wordpress (risk of being suspended due to high CPU/Memory usage) so I recently started installing/exploring/learning Joomla instead. But now I'm suspended... Could you please:- explain why I'm suspended so I can prevent it from happening again- restore my account? Thnx / Best regards!
wolstech Posted June 29, 2020 Posted June 29, 2020 Your account filled up /tmp yesterday, which caused downtime for everyone else on the server. Something on your account is not cleaning up after itself like it should be. Did you upload a large number of components for Joomla through its web interface by chance (I've seen Joomla leave stuff behind if something like installing a theme fails)? Unsuspended.
Krydos Posted June 29, 2020 Posted June 29, 2020 Your account used over 2.1 GB of space on /tmp and caused several hours of downtime for the thousands of other accounts on our best server. That's why you were suspended.
tstamphaus Posted June 29, 2020 Author Posted June 29, 2020 Wow, sorry for that. My apologies. Unintended.One of the first things starting with Joomla was indeed installing and checking some templates. Havn't done anything else yet. Joomlashine was the largest one. I suspect that one caused trouble. Makes me doubt about the switch again. I know enough about Wordpress, Joomla is new to me and seems more complex. But I'll check and keep checking the tmp-directory every now and than. Best regards / Thanks.
Krydos Posted June 30, 2020 Posted June 30, 2020 The best way to fix this is to edit your scripts to use /home/tstamp/tmp instead of /tmp. That way if something goes haywire you only take out your own account, not the whole server. 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now