Ashoat

Do any of these services allow me to prevent my email from being publicly available?

Did you add the user to the specific database?

I'm scheduling some downtime Friday, March 19th to get ASP.NET back online. I'm not really sure how long it'll last, but hopefully the process won't be too drawn out. After this, we should be able to retake first place on free-webhosts.com. Note to self: remember to add back /var/cpanel/mgmt_queue/apache_update_no_restart. PS: Happy 5th birthday, HelioHost!

You didn't point leolink.net's nameservers to HelioHost. Instead, you created an A record pointing to HelioNet. You need to point the nameservers first.

Don't worry, HelioHost isn't going to close. We've been around for five years now Okay, sure, but we'd need another server that could handle the mailing list. Does any server out there handle mailing lists for free?

Okay, this issue should be fixed.

The issue was that the filesystem was corrupted. This resulted in filesystem quota operations breaking the kernel scheduler. This shouldn't happen, and can only be the result of a bug in the Linux kernel. Anyways, I turned off quotas, but that left the corrupted filesystem read-only. I had to down the system for a filesystem check (day-long process) and then reboot the machine, then turn on the quotas again. Everything seems to be functioning now.

This is some really confusing stuff, but I think I've figured out what the issue was. I'll try to keep you guys updated.

1) Do not add the domain until Server Load, available under "Service Status" from the left panel of cPanel, is below 4. 2) Only add it once. 3) Wait 24 hours after adding. Try again now, following those three steps I am not seeing this issue. Regardless, you must open a new ticket if you have a new issue. This thread is about addon domain problems.

naibed: that domain "kliplagu.da.ru" doesn't seem to be pointed anywhere. Please point it to the nameservers ns1.heliohost.org and ns2.heliohost.org.

It's been three days without a response. I'm closing this thread - open a new one if you have continuing concerns.

SoLaaR: Okay, try again now.

No problem

manustays: It takes 24 hours. Everything seems to be working now. SoLaaR: Did you try to register the same domain twice?

I sent an email from an external account and it worked. You're probably logging in wrong, or something.

serkan, manustays, tattee, SoLaaR: try again now.

I'm seeing kw@ecurrentz.com's email from Horde just fine. I had to change the password to take a look, though. I've PM'd you the new password.

Sorry, but this is just the server being slow. We have a lot of accounts and we very often we have periods of high load on the server. Besides that, though, your application is probably pretty heavyweight. You might want to trim it down, or switch to something that requires less resources.

[Mon Mar 08 12:40:53 2010] [error] [client 69.91.143.154] mod_wsgi (pid=3709): Exception occurred processing WSGI script '/home/stanlly/public_html/dispatch.wsgi'. [Mon Mar 08 12:40:53 2010] [error] [client 69.91.143.154] Traceback (most recent call last): [Mon Mar 08 12:40:53 2010] [error] [client 69.91.143.154] File "/home/stanlly/public_html/dispatch.wsgi", line 15, in application [Mon Mar 08 12:40:53 2010] [error] [client 69.91.143.154] return _application(environ, start_response) [Mon Mar 08 12:40:53 2010] [error] [client 69.91.143.154] File "/usr/lib/python2.4/site-packages/django/core/handlers/wsgi.py", line 245, in __call__ [Mon Mar 08 12:40:53 2010] [error] [client 69.91.143.154] response = middleware_method(request, response) [Mon Mar 08 12:40:53 2010] [error] [client 69.91.143.154] File "/usr/lib/python2.4/site-packages/django/contrib/sessions/middleware.py", line 36, in process_response [Mon Mar 08 12:40:53 2010] [error] [client 69.91.143.154] request.session.save() [Mon Mar 08 12:40:53 2010] [error] [client 69.91.143.154] File "/usr/lib/python2.4/site-packages/django/contrib/sessions/backends/db.py", line 51, in save [Mon Mar 08 12:40:53 2010] [error] [client 69.91.143.154] obj = Session( [Mon Mar 08 12:40:53 2010] [error] [client 69.91.143.154] File "/usr/lib/python2.4/site-packages/django/contrib/sessions/backends/base.py", line 152, in _get_session_key [Mon Mar 08 12:40:53 2010] [error] [client 69.91.143.154] self._session_key = self._get_new_session_key() [Mon Mar 08 12:40:53 2010] [error] [client 69.91.143.154] File "/usr/lib/python2.4/site-packages/django/contrib/sessions/backends/base.py", line 144, in _get_new_session_key [Mon Mar 08 12:40:53 2010] [error] [client 69.91.143.154] if not self.exists(session_key): [Mon Mar 08 12:40:53 2010] [error] [client 69.91.143.154] File "/usr/lib/python2.4/site-packages/django/contrib/sessions/backends/db.py", line 25, in exists [Mon Mar 08 12:40:53 2010] [error] [client 69.91.143.154] Session.objects.get(session_key=session_key) [Mon Mar 08 12:40:53 2010] [error] [client 69.91.143.154] File "/usr/lib/python2.4/site-packages/django/db/models/manager.py", line 120, in get [Mon Mar 08 12:40:53 2010] [error] [client 69.91.143.154] return self.get_query_set().get(*args, **kwargs) [Mon Mar 08 12:40:53 2010] [error] [client 69.91.143.154] File "/usr/lib/python2.4/site-packages/django/db/models/query.py", line 300, in get [Mon Mar 08 12:40:53 2010] [error] [client 69.91.143.154] num = len(clone) [Mon Mar 08 12:40:53 2010] [error] [client 69.91.143.154] File "/usr/lib/python2.4/site-packages/django/db/models/query.py", line 81, in __len__ [Mon Mar 08 12:40:53 2010] [error] [client 69.91.143.154] self._result_cache = list(self.iterator()) [Mon Mar 08 12:40:53 2010] [error] [client 69.91.143.154] File "/usr/lib/python2.4/site-packages/django/db/models/query.py", line 238, in iterator [Mon Mar 08 12:40:53 2010] [error] [client 69.91.143.154] for row in self.query.results_iter(): [Mon Mar 08 12:40:53 2010] [error] [client 69.91.143.154] File "/usr/lib/python2.4/site-packages/django/db/models/sql/query.py", line 287, in results_iter [Mon Mar 08 12:40:53 2010] [error] [client 69.91.143.154] for rows in self.execute_sql(MULTI): [Mon Mar 08 12:40:53 2010] [error] [client 69.91.143.154] File "/usr/lib/python2.4/site-packages/django/db/models/sql/query.py", line 2368, in execute_sql [Mon Mar 08 12:40:53 2010] [error] [client 69.91.143.154] cursor = self.connection.cursor() [Mon Mar 08 12:40:53 2010] [error] [client 69.91.143.154] File "/usr/lib/python2.4/site-packages/django/db/backends/__init__.py", line 81, in cursor [Mon Mar 08 12:40:53 2010] [error] [client 69.91.143.154] cursor = self._cursor() [Mon Mar 08 12:40:53 2010] [error] [client 69.91.143.154] File "/usr/lib/python2.4/site-packages/django/db/backends/sqlite3/base.py", line 170, in _cursor [Mon Mar 08 12:40:53 2010] [error] [client 69.91.143.154] self.connection = Database.connect(**kwargs) [Mon Mar 08 12:40:53 2010] [error] [client 69.91.143.154] OperationalError: unable to open database file

Sounds good

No problem

alex82, naibed: okay, try now.

OK, you've been granted a dedicated IP.

Nothing. This issue was probably encountered during a period of high server load.

Yeah, a lot of free mail providers block us. Can you try signing up with a different username?