Krydos

Count: 17 Time=9.89s (168s) Lock=0.45s (7s) Rows=0.0 (0), b2scs[b2scs]@localhost DELETE FROM `joomla_session` WHERE `time` < 'S' -- Count: 4 Time=40.89s (163s) Lock=0.14s (0s) Rows=7.2 (29), b2scs[b2scs]@localhost SELECT m.id, m.title, m.module, m.position, m.content, m.showtitle, m.params, mm.menuid FROM joomla_modules AS m LEFT JOIN joomla_modules_menu AS mm ON mm.moduleid = m.id -- Count: 7 Time=19.57s (137s) Lock=0.27s (1s) Rows=0.0 (0), b2scs[b2scs]@localhost INSERT INTO `joomla_session` (`session_id`, `client_id`, `guest`, `time`, `userid`, `username`) VALUES ('S', N, N, 'S', N, 'S') -- Count: 8 Time=14.97s (119s) Lock=0.01s (0s) Rows=0.0 (0), b2scs[b2scs]@localhost INSERT INTO `joomla_updates` (`update_site_id`,`name`,`description`,`element`,`type`,`folder`,`client_id`,`version`,`detailsurl`,`infourl`) VALUES ('S','S','S','S','S','S','S','S','S','S') -- Count: 55 Time=1.63s (89s) Lock=0.06s (3s) Rows=27.0 (1486), b2scs[b2scs]@localhost SELECT `update_id` FROM `joomla_updates` WHERE element = 'S' AND type = 'S' AND client_id = 'S' AND folder = 'S' -- Count: 159 Time=0.52s (82s) Lock=0.02s (2s) Rows=1.9 (302), b2scs[b2scs]@localhost SELECT a.fulltext, a.id, a.title, a.alias, a.introtext, a.state, a.catid, a.created, a.created_by, a.created_by_alias, a.modified, a.modified_by, a.publish_up, a.publish_down, a.images, a.urls, a.attribs, a.metadata, a.metakey, a.metadesc, a.access, a.hits, a.featured,a.fulltext, a.id, a.title, a.alias, a.introtext, a.state, a.catid, a.created, a.created_by, a.created_by_alias, a.modified, a.modified_by, a.publish_up, a.publish_down, a.images, a.urls, a.attribs, a.metadata, a.metakey, a.metadesc, a.access, a.hits, a.featured,c.title AS category_title, c.path AS category_route, c.access AS category_access, c.alias AS category_alias,CASE WHEN a.created_by_alias > 'S' THEN a.created_by_alias ELSE ua.name END AS author,ua.email AS author_email,contact.id as contactid,parent.title as parent_title, parent.id as parent_id, parent.path as parent_route, parent.alias as parent_alias,ROUND(v.rating_sum / v.rating_count, N) AS rating, v.rating_count as rating_count,c.published, CASE WHEN badcats.id is null THEN c.published ELSE N END AS parents_published FROM joomla_content AS a LEFT JOIN joomla_content_frontpage AS fp ON fp.content_id = a.id -- Count: 4 Time=18.33s (73s) Lock=0.14s (0s) Rows=0.0 (0), b2scs[b2scs]@localho st UPDATE `joomla_update_sites` SET `last_check_timestamp` = 'S' WHERE `update_site_id` = 'S' -- Count: 49 Time=0.97s (47s) Lock=0.02s (1s) Rows=2.0 (98), b2scs[b2scs]@localhost SELECT c.*, CASE WHEN CHAR_LENGTH(c.alias)!=N THEN CONCAT_WS('S', c.id, c.alias) ELSE c.id END as slug,COUNT(i.`id`) AS numitems FROM joomla_categories as c LEFT JOIN joomla_categories AS s ON (s.lft <= c.lft AND s.rgt >= c.rgt) OR (s.lft > c.lft AND s.rgt < c.rgt) -- Count: 1 Time=39.22s (39s) Lock=0.04s (0s) Rows=11.0 (11), b2scs[b2scs]@localhost SELECT m.id, m.title, m.module, m.position, m.content, m.showtitle, m.params, mm.menuid FROM joomla_modules AS m LEFT JOIN joomla_modules_menu AS mm ON mm.moduleid = m.id

Unfortunately, python is heavily tied to cPanel, so if we upgrade the default version of python it could break a lot of other functionality. The good news is that multiple versions of python can coexist easily on the same server without interfering with each other; you just use different shebang lines to access the version that you need.

What is the file name of the .war file?

Ok, I finally got around to testing some of this stuff for you. Yes, SFTP only works for the root FTP account so that won't work for you. I set up a FTP account that only has access to one subdirectory, and successfully connected to it with FTP protocol with TLS. I tested this on both Johnny and Stevie. Here are some example settings that work with Filezilla. Just replace the portions in <> with your information: Host: ftp.<domain>.heliohost.org Port: 21 Protcol: FTP Encryption: Require explicit FTP over TLS Logon type: Normal User: <ftpusername>@<domain>.heliohost.org Password: <ftppassword> The first time you connect there will be a popup asking if you want to trust the self-signed SSL certificate. Let us know if you're still having trouble connecting to FTPS.

What server is your account located on, and which version of python are you using?

I recommend looking at http://heliohost.grd.net.pl/monitor/ and choosing a time when the server load is load.

Well, if you choose "every minute" then you would be running 1440 crons per day which is 1438 more than you're allowed and your account will be suspended. If you choose "every five minutes" then you would be running 288 crons per day which is 286 more than you're allowed and your account will be suspended. If you choose "twice an hour" then you would be running 48 crons per day which is 26 more than you're allowed and your account will be suspended. If you choose "once an hour" then you would be running 24 crons per day which is 22 more than you're allowed and your account will be suspended. If you choose any of the other options you should be fine as long as you don't set up multiple jobs. For instance if you choose "once a day" but then have 3 different jobs that all said "once a day" that would be a total of 3 cron jobs per day and your account will be suspended. I also recommending setting your cron jobs to run at random times of the day. For some reason everyone thinks their crons need to run at exactly midnight or exactly 3:00 pm or whatever. However, if everyone else crons are running at that same time then the server load spikes up and accounts get suspended for it. If you choose a random time like 1:39am then you have even less chance of being suspended.

I've got no problem running commands for you, but I'm not going to run any random command that any random person posts here. Furthermore, if that command just creates tables on a database, wouldn't it be easier to just run the command on your local machine, export the database, and import the .sql to a database hosted on Heliohost. That way it doesn't matter to us what the command does or doesn't do.

Your site is working fine for me but this information might help you at diagnosing 500 internal server errors in the future: Your post title says queued though. If you see the queued page when you visit your domain that means that you added your domain 24 hours or less ago or you just haven't cleared your browser cache. Sometimes browsers cache the queued page and can continue showing it for weeks when your site is actually working for everyone else.

I didn't write the account creation system, but I suspect it truncates the passwords sometimes when they are really long or maybe if they contain strange characters. I doubt you're going to create another account again, but if you do you could try starting with a shorter password using [A-Za-z0-9] to make it a bit simpler and let us know if it works any better. Obviously longer, randomer, more bizarre character passwords are stronger, but my guess would be that some characters are removed to prevent database injection.

Database tables?

Just wanted to make sure since you seem to miss my posts.

Yeah, no problem. It is extra work for us to provide reports like this so we only provide the extra information if people ask. That said, I do wish more people were willing to try to fix things. Most users are just like "i suspnededed!!! k thanx luv u" and then they just get suspended again since they didn't change anything. Create another post in customer service for inquiries related to load. If you tack it onto this topic that is already marked as [solved] we are less likely to notice it. We keep up to 48 hours of MySQL load data at any time.

What do you mean it works fine, but it doesn't work? Are you saying that the author of the flash .swf code claims it works in all browsers? Does it work on another server but not Heliohost? Are you saying that it doesn't work in one browser, but does in some others?

Yeah, but what does it do? If the instructions included the command rm -rf / would you do it just because it was in the instructions?

It wasn't invisible, but you definitely missed it. If you haven't yet I would also recommend reading through and doing some of the suggestions in this link http://v1.srcnix.com/2010/02/10/7-tips-to-prevent-php-running-out-of-memory/ I already linked it to you once, but since your main problem is memory usage it could probably help you.

After seeing these two queries: Count: 4 Time=365.80s (1463s) Lock=0.01s (0s) Rows=41.0 (164), b2scs[b2scs]@localhost SELECT folder AS type, element AS name, params FROM joomla_extensions WHERE enabled >= N AND type ='S' AND state >= N AND access IN (N,N,N) -- Count: 1 Time=205.52s (205s) Lock=0.00s (0s) Rows=11.0 (11), b2scs[b2scs]@localhost SELECT m.id, m.title, m.module, m.position, m.content, m.showtitle, m.params, mm.menuid FROM joomla_modules AS m LEFT JOIN joomla_modules_menu AS mm ON mm.moduleid = m.id it's no wonder you got suspended, but here are some other of your high load queries too: Count: 17 Time=40.39s (686s) Lock=0.34s (5s) Rows=0.0 (0), b2scs[b2scs]@localhost INSERT INTO `joomla_session` (`session_id`, `client_id`, `time`) VALUES ('S', N, 'S') -- Count: 23 Time=29.61s (681s) Lock=0.29s (6s) Rows=0.3 (7), b2scs[b2scs]@localhost SELECT `data` FROM `joomla_session` WHERE `session_id` = 'S' -- Count: 17 Time=26.71s (454s) Lock=0.10s (1s) Rows=0.0 (0), b2scs[b2scs]@localhost UPDATE joomla_content SET hits = hits + N WHERE id = N -- Count: 13 Time=34.71s (451s) Lock=0.05s (0s) Rows=0.0 (0), b2scs[b2scs]@localhost INSERT INTO `joomla_updates` (`update_site_id`,`name`,`description`,`element`,`type`,`folder`,`client_id`,`version`,`detailsurl`,`infourl`) VALUES ('S','S','S','S','S','S','S','S','S','S') -- Count: 16 Time=25.43s (406s) Lock=0.32s (5s) Rows=0.0 (0), b2scs[b2scs]@localhost UPDATE `joomla_session` SET `data` = 'S' , `time` = 'S' -- Count: 12 Time=33.21s (398s) Lock=0.01s (0s) Rows=0.0 (0), b2scs[b2scs]@localhost DELETE FROM `joomla_session` WHERE `time` < 'S' -- Count: 185 Time=1.82s (336s) Lock=0.02s (3s) Rows=25.6 (4744), b2scs[b2scs]@localhost SELECT `update_id` FROM `joomla_updates` WHERE element = 'S' AND type = 'S' AND client_id = 'S' AND folder = 'S' -- Count: 10 Time=31.80s (317s) Lock=0.11s (1s) Rows=8.1 (81), b2scs[b2scs]@localhost SELECT m.id, m.title, m.module, m.position, m.content, m.showtitle, m.params, mm.menuid FROM joomla_modules AS m LEFT JOIN joomla_modules_menu AS mm ON mm.moduleid = m.id -- Count: 4 Time=41.86s (167s) Lock=0.16s (0s) Rows=0.0 (0), b2scs[b2scs]@localhost UPDATE joomla_categories SET hits = hits + N WHERE id = N -- Count: 5 Time=28.03s (140s) Lock=0.01s (0s) Rows=0.0 (0), b2scs[b2scs]@localhost SELECT `session_id` FROM `joomla_session` WHERE `session_id` = 'S' LIMIT N, N -- Count: 3 Time=38.19s (114s) Lock=0.00s (0s) Rows=0.0 (0), b2scs[b2scs]@localhost SELECT `extension_id` FROM `joomla_extensions` WHERE element = 'S' AND type = 'S' AND client_id = 'S' AND folder = 'S' -- Count: 1 Time=56.90s (56s) Lock=0.14s (0s) Rows=1.0 (1), b2scs[b2scs]@localhost SELECT id, password FROM joomla_users WHERE username='S' -- Count: 1 Time=53.11s (53s) Lock=0.00s (0s) Rows=1.0 (1), b2scs[b2scs]@localhost Select Distinct SQL_CALC_FOUND_ROWS record.* From joomla_facileforms_records As record Order By record.submitted ASC Limit N, N -- Count: 1 Time=40.48s (40s) Lock=0.00s (0s) Rows=1.0 (1), b2scs[b2scs]@localhost SELECT params FROM joomla_extensions WHERE folder = "S" AND element ="S" -- Count: 1 Time=36.70s (36s) Lock=0.00s (0s) Rows=41.0 (41), b2scs[b2scs]@localhost SELECT folder AS type, element AS name, params FROM joomla_extensions WHERE enabled >= N AND type ='S' AND state >= N AND access IN (N,N,N,N)

%CPU 15.0 /usr/bin/php /home1/gaddons/public_html/forum/posting.php

Select custom DNS and type ns1.heliohost.org and ns2.heliohost.org. Then cPanel will handle the A records and MX records automatically.

Each account can have 1 or 0 .heliohost.org domains. If you would like additional free domains I would recommend registering a .tk at http://dot.tk/

Deployed. http://infopar.heliohost.org/infopar_catechesi/

Your question is very difficult for me to understand, but are you asking if you can have two different .heliohost.org domains? One like domain1.heliohost.org and another domain2.heliohost.org?

I don't really understand what the problem is, because you even include in your own post how to fix it? cPanel isn't actually something that Heliohost wrote, we just bought a license for it and run it on our servers. If it was a huge critical error that only affected Heliohost and the cPanel developers showed no signs of ever fixing it then it would be worth it for me to get into the source code and make some modifications, but this is just a tiny cosmetic flaw that results in a popup box if you do a really unique series of actions. It might even be fixed already in a newer version of cPanel that we haven't upgraded to yet. I don't think it really matters either way. If the error prevented some critical action from taking place like you would never be able to create a new directory through File Manager or FTP ever again then it would be worth the effort to fix it. Maybe I just don't understand your post enough to recognize why this is such a life threatening error for you. Anyways, if it makes you feel better I was able to recreate the same popup box as you describe by following the exact steps that you listed and not any other way. No amount of recreating your account will fix something that affects the whole server.

Your account was resuspended for failure to take care of the malware problem during your allotted 24 hour period. The offending files have been deleted, and your account has been manually unsuspended. If you still see the suspended page then you should try clearing your browsers cache. Since you obviously have no idea what is going on, I'll explain it in really simple terms for you. If you don't secure your website hackers can upload malicious files like the one that was detected by our virus scanner. We suspended your account to let you know about the problem. You asked for an unsuspension, we told you what the problem was, but you didn't fix it. What a c99 shell does is allow hackers to upload whatever they want or change your files. It might not have anything to do with passwords if you upload this malicious script for the hacker in the form of a free theme or plugin. If you don't secure your website or if you keep uploading these types of files yourself your account will continue to be suspended for malware or defaced by the owners of the malware. I get the feeling that you're trying to imply that Heliohost is insecure, but that's incorrect. Our servers are quite secure, but it's your responsibility to make sure everything you upload to your account is secure.

General ideas on how attacks occur, what software is vulnerable to what types of attacks, and especially discussion on how to guard against those types of attacks are ok. Using Heliohost's servers to host attack tools, attacking other servers with scripts on Heliohost, or coordinating attacking certain targets is not ok. There are tons of ignorant users out there that don't understand why or how their websites keep getting defaced, and can't come close to understanding how to prevent it from happening again so bonus points to anyone who can help users like that on these forums. Hacking is kind of like STDs. If everyone ignores it, refuses to talk about it, and learns nothing it only gets worse. The more knowledge people have the better off we all are.