Hello!! last few days we get error to load web interface, Class ‘CI_Controller’ not found
as i have read there must be a problem with the php , anyone who has similar problem and has sort it out ??
Thanks
Could you check the disk space. Example df -h command. Maybe the disk is full.
Most of the time is caused for lower disk space.
Clean up logs and free space (specially in the ROOT partition)
Other times is the mysql. Restart the server and usually work (after cleaning space)
Yup that’s seems to be the problem , i have wape out logs, thanks for your answer!!
hello all,
can you please guide me on where to delete the logs causing this Class ‘CI_Controller’ not found error. I have a newly installed server with so much space on it bit it keeps saying that the disk space is full. is there a workaround to increase its size.
Filesystem Size Used Avail Use% Mounted on
devtmpfs 7.8G 0 7.8G 0% /dev
tmpfs 16G 0 16G 0% /dev/shm
tmpfs 16G 16G 0 100% /run
tmpfs 7.8G 0 7.8G 0% /sys/fs/cgroup
/dev/md2 212G 8.7G 193G 5% /
/dev/md0 487M 142M 316M 31% /boot
Class ‘CI_Controller’ not found
When I run this dmesg | less, these error is coming up.
[328009.477906] systemd-journald[631]: Failed to open runtime journal: No space left on device
[328009.478471] systemd-journald[631]: Failed to open runtime journal: No space left on device
[328009.914664] systemd-journald[631]: Failed to open runtime journal: No space left on device
[328009.916112] systemd-journald[631]: Failed to open runtime journal: No space left on device
[328009.916742] systemd-journald[631]: Failed to save stream data /run/systemd/journal/streams/7:40318088: No space left on device
[328009.920548] systemd-journald[631]: Failed to open runtime journal: No space left on device
[328009.921247] systemd-journald[631]: Failed to open runtime journal: No space left on device
[328010.109034] systemd-journald[631]: Failed to open runtime journal: No space left on device
[328010.280470] systemd-journald[631]: Failed to open runtime journal: No space left on device
[328010.310422] systemd-journald[631]: Failed to open runtime journal: No space left on device
[328010.490775] systemd-journald[631]: Failed to open runtime journal: No space left on device
[328013.745689] systemd-journald[631]: Failed to open runtime journal: No space left on device
[328013.746282] systemd-journald[631]: Failed to open runtime journal: No space left on device
[328013.964203] systemd-journald[631]: Failed to open runtime journal: No space left on device
[328013.965183] systemd-journald[631]: Failed to open runtime journal: No space left on device
[328015.876597] systemd-journald[631]: Failed to open runtime journal: No space left on device
[328016.094291] systemd-journald[631]: Failed to open runtime journal: No space left on device
[328019.241521] systemd-journald[631]: Failed to open runtime journal: No space left on device
[328019.242417] systemd-journald[631]: Failed to open runtime journal: No space left on device
[328019.243236] systemd-journald[631]: Failed to open runtime journal: No space left on device
[328023.215260] systemd-journald[631]: Failed to open runtime journal: No space left on device
[328023.215971] systemd-journald[631]: Failed to open runtime journal: No space left on device
did you sort this out??
Configure your logs to be checked daily and to rotate if above a certain size. The current install script does most of that for you so check your install against the current script and change it manually if necessary. Also, change weekly rotation check to daily and keep the number of rotation copies low. Maybe 4 or 5 at the most.
Hello All,
We are getting same error any one help me.
An Error Was Encountered
Class ‘CI_Controller’ not found
df -h
Filesystem Size Used Avail Use% Mounted on
udev 2.0G 0 2.0G 0% /dev
tmpfs 395M 47M 348M 12% /run
/dev/vda1 79G 5.5G 69G 8% /
tmpfs 2.0G 0 2.0G 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 2.0G 0 2.0G 0% /sys/fs/cgroup
tmpfs 395M 0 395M 0% /run/user/0
root@server3:/etc/init.d#
root@server3:/etc/init.d# systemctl status mysql
Unit mysql.service could not be found.
root@server3:/etc/init.d#
root@server3:/etc/init.d#
Mysql service is not found, please check if its installed while the script was running ?
Hello @palak
We are try three to four time install get the same error we have download the script from the below link.
Which version of ASTPP did you install?
@tai36 , the db connection details available under astpp-config.conf, are you able to connect to mysql using those details?
I think that means it can’t connect to MySQL. One common cause of this is that legacy authentication is not enabled. Another one is that mysql odbc connector is not installed or configured properly. Or maybe MySQL is not starting for some reason, like a full disk.