Krydos

For anyone who reads this thread, it is possible to install apache modules upon user request, but the list of available modules is fairly limited, and would need to work with the rest of our system. Mod_xsendfile is not on that list of available modules however.

The file that caused the high spike load suspension is /home/sohamb03/public_html/sohamb03.us.to/proxy/index.php You say you weren't using the proxy, but that doesn't mean someone else wasn't using it. You posted a link to it on a forum that gets thousands of page views per day. People love to find new open proxies to use. Some use them to help conceal their illegal activity on the internet, and some just want as many ways as possible to circumvent their oppressive government's watchful eyes. Either way, proxies on the internet tend to get a lot of traffic once they're discovered.

During an apache restart the system detected corruption in the ssl database, which means that a full ssl database rebuild was required before apache would start. Unfortunately it take a very long time to rebuild the ssl database. It should all be working again now.

Try this https://php-download.com/

Did this work for you, pieviks?

Unsuspended. Fix it quickly.

21-Jul-2019 20:16:00.912 SEVERE [ContainerBackgroundProcessor[StandardEngine[Catalina]]] org.apache.catalina.core.ContainerBase.addChildInternal ContainerBase.addChild: start: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/luqman_backend]] at org.apache.catalina.util.LifecycleBase.handleSubClassException(LifecycleBase.java:441) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:198) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:743) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:719) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:703) at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:986) at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1858) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75) at java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:112) at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:772) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:426) at org.apache.catalina.startup.HostConfig.check(HostConfig.java:1629) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:304) at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:123) at org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1176) at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1398) at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1402) at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1370) at java.lang.Thread.run(Thread.java:748) Caused by: org.springframework.jmx.export.UnableToRegisterMBeanException: Unable to register MBean [HikariDataSource (HikariPool-3)] with key 'dataSource'; nested exception is javax.management.InstanceAlreadyExistsException: com.zaxxer.hikari:name=dataSource,type=HikariDataSource at org.springframework.jmx.export.MBeanExporter.registerBeanNameOrInstance(MBeanExporter.java:625) at org.springframework.jmx.export.MBeanExporter.lambda$registerBeans$2(MBeanExporter.java:551) at java.util.HashMap.forEach(HashMap.java:1289) at org.springframework.jmx.export.MBeanExporter.registerBeans(MBeanExporter.java:551) at org.springframework.jmx.export.MBeanExporter.afterSingletonsInstantiated(MBeanExporter.java:434) at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:862) at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:877) at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:549) at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:140) at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:742) at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:389) at org.springframework.boot.SpringApplication.run(SpringApplication.java:311) at org.springframework.boot.web.servlet.support.SpringBootServletInitializer.run(SpringBootServletInitializer.java:151) at org.springframework.boot.web.servlet.support.SpringBootServletInitializer.createRootApplicationContext(SpringBootServletInitializer.java:131) at org.springframework.boot.web.servlet.support.SpringBootServletInitializer.onStartup(SpringBootServletInitializer.java:91) at org.springframework.web.SpringServletContainerInitializer.onStartup(SpringServletContainerInitializer.java:171) at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5098) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) ... 19 more Caused by: javax.management.InstanceAlreadyExistsException: com.zaxxer.hikari:name=dataSource,type=HikariDataSource at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:437) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerWithRepository(DefaultMBeanServerInterceptor.java:1898) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:966) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:900) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:324) at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:522) at org.springframework.jmx.support.MBeanRegistrationSupport.doRegister(MBeanRegistrationSupport.java:137) at org.springframework.jmx.export.MBeanExporter.registerBeanInstance(MBeanExporter.java:671) at org.springframework.jmx.export.MBeanExporter.registerBeanNameOrInstance(MBeanExporter.java:615) ... 36 more

There you go https://krydos2.heliohost.org/cgi-bin/modules36.py

By not filling /tmp? If you have any scripts that write or read from /tmp you need to edit them and have them write and read from /home/neverfor/tmp instead. That way your scripts will only crash your account rather than crashing all the other thousands of accounts on your server.

Remote access enabled.

You can find the exim logs in /var/log/exim4/

Closing due to inactivity.

I'm assuming you want the user ereyes_entipisa to have access to the database ereyes_entipi, and the user ereyes_sigesp to have access to the database ereyes_siges?

I installed the files for you. You need to create the mysql database for it and then you can finish the installation.

Please change your nameservers to ns1.heliohost.org and ns2.heliohost.org.

It looks like there is an active Tommy account with the username izmtky that is associated with this email address.

It looks like there is an active Tommy account with the username izmtky that is associated with this email address.

It looks like there is an active Tommy account with the username izmtky that is associated with this email address.

Please clear your browser cache.

You already have reverse DNS set up. Just google "reverse dns lookup" and type in your IP address, or run the command dig +noall +answer -x 216.218.228.90

The heliohost2.gmail.com in the SOA record is actually an email address, not a subdomain. Ashoat got tired of all of the account creation emails being sent to his personal account so I set up that junk mail box because cpanel requires some admin email address. Any domain that uses Heliohost DNS will have that same SOA record.

Done. You should now be able to log in and your website should start working within 2 hours.

Done. You should now be able to log in and your website should start working within 2 hours.

Does it work using http (instead of https)?

Unarchiving...