Krydos

The postgis extension has been created on that database.

By default mysql uses the server's timezone, which is set to UTC. Depending on your scripting language it's probably easier to set the timezone before you do your queries. For instance in php you could use date_default_timezone_set("America/Los_Angeles"); You can also change the timezone in your raw mysql queries by using convert_tz select thing, convert_tz(timestamp, @@session.time_zone, '-08:00') from stuff;

In your application manager you put that your node application is located at /home/robev/node/ and when I look at your account there is no node directory in /home/robev/.

org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'fileController': Unsatisfied dependency expressed through field 'fileStorageService'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'fileStorageService' defined in file [/opt/tomcat/apache-tomcat-8.5.24/webapps/ternsjo_Troff/WEB-INF/classes/com/slimsimapps/troff/service/FileStorageService.class]: Bean instantiation via constructor failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.slimsimapps.troff.service.FileStorageService]: Constructor threw exception; nested exception is java.lang.NullPointerException at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.inject(AutowiredAnnotationBeanPostProcessor.java:643) ~[spring-beans-5.2.5.RELEASE.jar:5.2.5.RELEASE] at org.springframework.beans.factory.annotation.InjectionMetadata.inject(InjectionMetadata.java:130) ~[spring-beans-5.2.5.RELEASE.jar:5.2.5.RELEASE] at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor.postProcessProperties(AutowiredAnnotationBeanPostProcessor.java:399) ~[spring-beans-5.2.5.RELEASE.jar:5.2.5.RELEASE] at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1422) ~[spring-beans-5.2.5.RELEASE.jar:5.2.5.RELEASE] at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:594) ~[spring-beans-5.2.5.RELEASE.jar:5.2.5.RELEASE] at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:517) ~[spring-beans-5.2.5.RELEASE.jar:5.2.5.RELEASE] at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:323) ~[spring-beans-5.2.5.RELEASE.jar:5.2.5.RELEASE] at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222) ~[spring-beans-5.2.5.RELEASE.jar:5.2.5.RELEASE] at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:321) ~[spring-beans-5.2.5.RELEASE.jar:5.2.5.RELEASE] at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:202) ~[spring-beans-5.2.5.RELEASE.jar:5.2.5.RELEASE] at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:882) ~[spring-beans-5.2.5.RELEASE.jar:5.2.5.RELEASE] at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:878) ~[spring-context-5.2.5.RELEASE.jar:5.2.5.RELEASE] at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:550) ~[spring-context-5.2.5.RELEASE.jar:5.2.5.RELEASE] at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:141) ~[spring-boot-2.2.6.RELEASE.jar:2.2.6.RELEASE] at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:747) ~[spring-boot-2.2.6.RELEASE.jar:2.2.6.RELEASE] at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:397) ~[spring-boot-2.2.6.RELEASE.jar:2.2.6.RELEASE] at org.springframework.boot.SpringApplication.run(SpringApplication.java:315) ~[spring-boot-2.2.6.RELEASE.jar:2.2.6.RELEASE] at org.springframework.boot.web.servlet.support.SpringBootServletInitializer.run(SpringBootServletInitializer.java:152) [spring-boot-2.2.6.RELEASE.jar:2.2.6.RELEASE] at org.springframework.boot.web.servlet.support.SpringBootServletInitializer.createRootApplicationContext(SpringBootServletInitializer.java:132) [spring-boot-2.2.6.RELEASE.jar:2.2.6.RELEASE] at org.springframework.boot.web.servlet.support.SpringBootServletInitializer.onStartup(SpringBootServletInitializer.java:92) [spring-boot-2.2.6.RELEASE.jar:2.2.6.RELEASE] at org.springframework.web.SpringServletContainerInitializer.onStartup(SpringServletContainerInitializer.java:172) [spring-web-5.2.5.RELEASE.jar:5.2.5.RELEASE] at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5196) [catalina.jar:8.5.24] at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) [catalina.jar:8.5.24] at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:752) [catalina.jar:8.5.24] at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:728) [catalina.jar:8.5.24] at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:734) [catalina.jar:8.5.24] at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:986) [catalina.jar:8.5.24] at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1857) [catalina.jar:8.5.24] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [na:1.8.0_282] at java.util.concurrent.FutureTask.run(FutureTask.java:266) [na:1.8.0_282] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [na:1.8.0_282] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [na:1.8.0_282] at java.lang.Thread.run(Thread.java:748) [na:1.8.0_282]

Remote access enabled.

Remote access enabled and postgis extension created.

Remote access enabled.

That account is suspended for Phishing. HelioHost does not tolerate phishing activity of any kind, and for security reasons will not unsuspend, back up, or delete an account that was involved in phishing. You will need to create a new account and restore any backup you may have. Please be aware that you will not be able to reuse any domains on your suspended account, and will need to pick a new username. We apologize for any inconvenience this may have caused.

Can you post the full error?

Remote access enabled.

There you go # dig +noall +answer -x 64.71.156.101 101.156.71.64.in-addr.arpa. 86400 IN CNAME 101.subnet96.156.71.64.in-addr.arpa. 101.subnet96.156.71.64.in-addr.arpa. 14400 IN PTR members.snipettemag.com.

Remote access enabled.

To clarify slightly: If you update your email address through cpanel it will take a few hours before you can log in to heliohost.org with the new email address. You can always log in to cpanel with your username, and your username will always work on the heliohost.org site too. Your email address will not sync to helionet though. The forums are a completely separate system, and if you want to change your email address on the forums you need to click your username in the top right on that black bar.

Sorry about that. You were blocked on the old Ricky server not on Tommy. I hadn't wiped the old Ricky blocked ips from the database yet, and the ip blocking module hasn't been installed on new Ricky yet, which would have wiped the firewall database for me. My fault for not clearing out all the old data yet.

If you had access to whm you'd be able to delete, edit, spy on, read, and access everything for all of the thousands of other accounts on your server. So... no. If you're trying to do something and you read a guide saying to log in to whm just let us know what you are trying to do and we can do it for you.

Handled via email.

So, the domain change script was written 1000 years ago when the servers spoke the cryptic language of xml-api. Gradually over the millennia the wizards of cpanel phased that language out and taught all the servers to speak all sorts of random short lived languages such as api2 uapi and stuff that we pretty much ignored because if it isn't broke don't fix it, right? At this point xml-api is completely unsupported, but oddly enough it still works, just not all the time, and no one knows why it works and it hasn't even supposed to work for like 500 years now or so. The new scripts use the latest most modern language of json-api and it always works. So when we rewrite the domain change page we will use json-api and it should always work, and then everyone can live happily ever after. The end.

There you go. http://hbchat.heliohost.us/

It looks like that error message is a bug in the particular version of cpanel that Tommy and Johnny are running. I just tested it on Ricky and it's fixed in that version of cpanel. As long as nothing goes wrong with the Ricky rebuild we can upgrade Tommy and Johnny's cpanel to the same version as Ricky eventually. There was another unrelated bug that someone found in Tommy and Johnny's version of cpanel so upgrading them was already on my todo list.

Try adding it now. Johnny always has a lot of load spikes, but today has been extra bad. When the load is high wacky things like this happen. If you want a more stable server with much lower load and better uptime we recommend Tommy.

The 7 day load chart shows your usage from 00:00 UTC until 23:59 UTC. So the next day will start in about 3.5 hours.

Unblocked.

It depends on the code, but processes should end themselves unless there is an infinite loop. Perhaps check your code and make sure that there is no chance of any loops getting stuck. You can also use cgi or cron to kill your processes yourself.

Most of your cpu and memory usage is coming from /home/goman60/public_html/index.cgi It looks like you've deleted the file, which doesn't stop the load because there are 3 of them already running. Would you like me to kill those processes for you?

It can take up to 15 minutes sometimes to get unblocked. You posted at 10 minutes so it probably finished unblocking you within a few minutes of your post. The SFTP username is the same as your cpanel username. This is not your email address, but rather the username jmlousa, and it has to be all lowercase. Your SFTP password is the same as your cpanel password. If you try to login to SFTP make sure your FTP client doesn't try over and over again. A lot of FTP clients will just try the wrong password over and over so quickly that you get blocked within a few seconds. If the cpanel password doesn't work for SFTP you can try changing your password to something else and trying again, but make sure you don't have too many failed attempts in a short amount of time.