This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Critical Error - [0100]
#1
Critical Error - [0100]
After running Sentora (1.0.3) for a couple of years, it started to stop working from time to time, without knowing what triggers the Critical Error - [0100]. 

I know when Sentora isn't running only when I don't get emails. 

The quick fix that I found is to do a sudo reboot.

Is there something I can do to fix this?
Reply
Thanks given by:
#2
RE: Critical Error - [0100]
First thought is HD space. If your logs or clients are using more disk space then your HD can handle it will shut down.
If Sentora has been working for years without problems, disk storage space is the first thing to check.

Log files in general can eat up a lot of space.

You also need to check which log files are so big. A client may have a 'bad' website that is posting a lot of errors to the logs making them grow fast.
-TGates - Project Council

SEARCH the Forums or read the DOCUMENTATION before posting!
Support Sentora and Donate: HERE

Find my support or modules useful? Donate to TGates HERE
Developers and code testers needed!
Contact TGates for more information
Reply
Thanks given by:
#3
RE: Critical Error - [0100]
(09-29-2017, 05:06 PM)TGates Wrote: First thought is HD space. If your logs or clients are using more disk space then your HD can handle it will shut down.
If Sentora has been working for years without problems, disk storage space is the first thing to check.

Log files in general can eat up a lot of space.

You also need to check which log files are so big. A client may have a 'bad' website that is posting a lot of errors to the logs making them grow fast.


Just checked and it's not that. The problems started after I installed AnchorCMS on one of the sites. Could one database be corrupted? 


http://snpy.in/28E1ri
Reply
Thanks given by:
#4
RE: Critical Error - [0100]
(09-29-2017, 07:05 PM)perte Wrote: Just checked and it's not that. The problems started after I installed AnchorCMS on one of the sites. Could one database be corrupted? 


http://snpy.in/28E1ri

try removing all db entries from AnchorCMS & remove the CMS completely. then check if you are still getting Error: "0100".

If you still are, check all clients logs, check server logs, check all available logs. That should determine what is casing the issue or direct you to a users site that is giving those errors.
-BetaTester3.0  ||  Just Another Sentora User. 

Did you know, Sentora has a full Support Documentation ?
If I helped +rep & Thanks is appreciated.
BTC: 1Bps3ZerDFDDnXJ9XdWtHhdhwsV4MVGLkw

Reply
Thanks given by:
#5
RE: Critical Error - [0100]
So, I've been checking the MySQL logs recently and found this:

PHP Code:
171004 13:37:22 [WarningUsing unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future releasePlease use the full name instead.
171004 13:37:22 [NotePlugin 'FEDERATED' is disabled.
171004 13:37:22 InnoDBThe InnoDB memory heap is disabled
171004 13
:37:22 InnoDBMutexes and rw_locks use GCC atomic builtins
171004 13
:37:22 InnoDBCompressed tables use zlib 1.2.8
171004 13
:37:22 InnoDBUsing Linux native AIO
171004 13
:37:22 InnoDBInitializing buffer poolsize 128.0M
171004 13
:37:22 InnoDBCompleted initialization of buffer pool
171004 13
:37:22 InnoDBhighest supported file format is Barracuda.
InnoDBThe log sequence number in ibdata files does not match
InnoDB
the log sequence number in the ib_logfiles!
171004 13:37:22  InnoDBDatabase was not shut down normally!
InnoDBStarting crash recovery.
InnoDBReading tablespace information from the .ibd files...
InnoDBRestoring possible half-written data pages from the doublewrite
InnoDB
buffer...
171004 13:37:22  InnoDBWaiting for the background threads to start
171004 13
:37:23 InnoDB5.5.44 startedlog sequence number 802606510
171004 13
:37:23 [NoteServer hostname (bind-address): '127.0.0.1'port3306
171004 13
:37:23 [Note  '127.0.0.1' resolves to '127.0.0.1';
171004 13:37:23 [NoteServer socket created on IP'127.0.0.1'.
171004 13:37:23 [NoteEvent SchedulerLoaded 0 events
171004 13
:37:23 [Note] /usr/sbin/mysqldready for connections.
Version'5.5.44-0ubuntu0.14.04.1'  socket'/var/run/mysqld/mysqld.sock'  port3306  (Ubuntu)
171004 13:37:24 [ERROR] /usr/sbin/mysqldTable './sentora_core/x_bandwidth' is marked as crashed and should be repaired
171004 13
:37:24 [WarningChecking table  './sentora_core/x_bandwidth' 

Coincidentally, I stopped getting emails after 13:30 - that's how I know my server is down. So I assume that there's something wrong here, right?
Reply
Thanks given by:


Possibly Related Threads…
Thread Author Replies Views Last Post
Repo update error hostingms 3 5 ,989 02-14-2024, 09:20 AM
Last Post: TGates
apt-get install mod_ssl ERROR CMs222 9 26 ,752 11-11-2022, 09:14 PM
Last Post: zustudios
Sentora debug and error files johnnyp 0 1 ,365 10-27-2022, 06:16 PM
Last Post: johnnyp

Forum Jump:


Users browsing this thread: 1 Guest(s)