"Internal Server Error"

PLEASE HELP!

Upon opening my company’s ERPNext site there is a message of “Internal Server Error.” I’m assuming that is internal server error is from ERP Next’s side. I’ve already created a github issue. Since ERPNext is crucial to our operations, can anyone tell me if this is being worked on as of 2/19/18?

Thank you!

“Internal Server Error.” is a catchall general message that needs diagnostic troubleshooting.

To post this as an issue is premature ERP Internal Server Error · Issue #12996 · frappe/erpnext · GitHub

Some suggestions -

Assuming you are hosted on erpnext.com, email support@erpnext.com your request to check your logs to identify the nature of your server error.

A screenshot or notes of what you were doing at the time when this occurred would help too.

3 Likes

Are you self-hosted? If you are hosted by ERPNext you should contact support. If you are self-hosted then you need to look at your server logs. We used to get Internal Server Error messages periodically, usually related to mariadb crashing due to insufficient memory.

How much RAM does your server have? If you login to the server there will potentially be an error message displayed which might help narrow it down. Throw it a reboot before worrying too much. When we went from 1 gig to 2 gigs of memory it never happened again. Make sure your machine has sufficient resources for the workload.

I have same error in a VPS with 2 GB RAM. The internal error I get is this [1]. I imagine I have to increase RAM more than 2GB.

Thanks

[1]

root@vps:/home/frappe# /etc/init.d/mysql status
● mariadb.service - MariaDB database server
Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
Drop-In: /etc/systemd/system/mariadb.service.d
└─migrated-from-my.cnf-settings.conf
Active: failed (Result: timeout) since Mon 2018-01-15 16:12:32 EET; 1min 3s ago
Process: 1507 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=0/SUCCESS)
Process: 1240 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= || VAR=`/usr/bin/galera_recovery`; [ $? -eq 0 ] && systemctl set-environment _WSREP_START_POSITION=$VAR || exit 1 (code=exited, status=0/SUCCESS)
Process: 1213 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
Process: 1199 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS)
Main PID: 1507 (code=exited, status=0/SUCCESS)
Status: "MariaDB server is down"

Jan 15 16:12:30 vps.domain.com mysqld[1507]: 2018-01-15 16:12:30 140358256498432 [Note] InnoDB: Starting shutdown...
Jan 15 16:12:30 vps.domain.com mysqld[1507]: 2018-01-15 16:12:30 140357341783808 [Note] InnoDB: Dumping buffer pool(s) to /var/lib/mysql/ib_buffer_pool
Jan 15 16:12:30 vps.domain.com mysqld[1507]: 2018-01-15 16:12:30 140357341783808 [Note] InnoDB: Instance 0, restricted to 4096 pages due to innodb_buf_pool_dump_pct=25
Jan 15 16:12:30 vps.domain.com mysqld[1507]: 2018-01-15 16:12:30 140357341783808 [Note] InnoDB: Buffer pool(s) dump completed at 180115 16:12:30
Jan 15 16:12:32 vps.domain.com mysqld[1507]: 2018-01-15 16:12:32 140358256498432 [Note] InnoDB: Shutdown completed; log sequence number 5003891853
Jan 15 16:12:32 vps.domain.com mysqld[1507]: 2018-01-15 16:12:32 140358256498432 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
Jan 15 16:12:32 vps.domain.com mysqld[1507]: 2018-01-15 16:12:32 140358256498432 [Note] /usr/sbin/mysqld: Shutdown complete
Jan 15 16:12:32 vps.domain.com systemd[1]: Failed to start MariaDB database server.
Jan 15 16:12:32 vps.domain.com systemd[1]: mariadb.service: Unit entered failed state.
Jan 15 16:12:32 vps.domain.com systemd[1]: mariadb.service: Failed with result 'timeout'.

@fabyc Yes, this is the same error we used to encounter. We went from a DigitalOcean droplet of 1gig to 2gigs. We have not has any issues since we bumped it up.

You may have a parameter in the /etc/my.cnf file which is set wrong (too high). you should be able to run a basic system on 1-2GB

Ty @clarkej for suggest to read ERP Internal Server Error · Issue #12996 · frappe/erpnext · GitHub

i follow there instruction and my web can up again :sweat_smile:

5 Likes