The email account was set up as an IMAP account.
The reason turned out to be the fact that the Inbox of the account contained many emails (>18.000) so I just moved all emails from the Inbox to an Archive folder and the problem was resolved.
I got my hands on a used HP Proliant server with P420i raid controller, however was unable to create a logical raid drive using the ACU. A message while booting shows “Hardware RAID support is disabled via NVRAM Configuration Setting“. It turns out the raid had been disabled by enabling hba mode.
This can be solved but it is a bit tricky. I used information from the following sources:
https://systemausfall.org/wikis/howto/Disable%20HP%20Proliant%20Hardware-RAID
http://downloads.linux.hpe.com/SDR/project/mcp/
https://wiki.debian.org/HP/ProLiant#HP_Repository
https://cdimage.debian.org/debian-cd/current-live/amd64/iso-hybrid/
sudo nano /etc/apt/sources.listdeb http://downloads.linux.hpe.com/SDR/repo/mcp jessie/current non-freesudo curl http://downloads.linux.hpe.com/SDR/hpPublicKey1024.pub | apt-key add -
sudo curl http://downloads.linux.hpe.com/SDR/hpPublicKey2048.pub | apt-key add -
sudo curl http://downloads.linux.hpe.com/SDR/hpPublicKey2048_key1.pub | apt-key add -
sudo curl http://downloads.linux.hpe.com/SDR/hpePublicKey2048_key1.pub | apt-key add -apt-get install ssaclissacli controller slot=0 showssacli controller slot=0 modify hbamode=offZoneminder version 1.37.28. The installation had been running for years without problem but somehwere in the 1.37 version problems started to occur. Some cameras did not give visible streams in Zoneminder from time to time. Checking the cameras video directly, they where ok, so the problem was in Zoneminder. Some cameras was “capturing” but analyzing 0 fps.
In the log there was lines like:
Restarting capture daemon for 6 CAMERA NAME, no image since startup. Startup time was 1671521356 – now 1671521366 > 5
And mostly interesting:
You have set the max video packets in the queue to 100. The queue is full. Either Analysis is not keeping up or your camera’s keyframe interval 50 is larger than this setting.
The reason for this is that the buffer setting for Maximum Image Buffer size (frames) is too low compared to the key frame interval setting in the camera. The higher key frame interval (which means lower bandwidth) means Image Buffer Size must be higher, consuming more RAM. So what you save in bandwidth, you will pay in RAM. Key frame interval is how often the camera sends a full image and between them just the difference. More seldom (higher key frame interval) means lower bandwidth but you need a bigger buffer in the server.
I set my cameras to deliver 5 fps with a key frame interval of 5 as they are on a remote location (not where the server is) and all video is streamed over the Internet to the server.
I changed the options for each camera, Console -> click on source -> Buffers and change Image Buffer Size (frames) (in my case set it to 3) and Maximum Image Buffer Size (frames) (in my case I could actually decrease it from 100 to just 55 because I reduced the fps and decreased the key frame interval in the camera).
Observe how memory is used after this. You need to balance the buffer sizes the cameras fps and key frame interval
Still it did not completely solve the problem. Only after changing Options -> System -> WATCH_MAX_DELAY from 5 to 45 and restart Zoneminder, the system started to show images for all feeds. It seems like 5 seconds for the capture to start was to little so it keept restarting the capture processes.
As a part of the investigation I had also changed /tmp into tmpfs according to some post I found online, so I did that also but it did not solve the problem. However, it improved performance so I let it be. Add the following line to /etc/fstab and reboot:
tmpfs /tmp tmpfs rw,nosuid,nodevAnother important thing when it comes to Zoneminder performance is to disable unused cameras. You can leave the camera in the Zoneminder configuration for later use but if it is going to be offline for a longer period, it is a good idea to disable it because a camera that is offline will put unecessary load on the Zoneminder server.
Go to Console -> click on source -> Source and set Capturing to None
Remember to put it back when the camera is online again 😉
If you need to monitor a VNC service without logging in, the following check_command can be used.
Edit your nagios configuration file and add:
# VNCdefine command{
command_name check_vnc
command_line $USER1$/check_tcp -H $HOSTADDRESS$ -p $ARG1$ -w 5 -c 8 -
e "RFB"
}
Then on the service you want to monitor use:
define service{
use generic-service ; Name of service template to use host_name
host_name MYHOSTNAME
service_description VNC
is_volatile 0
check_period 24x7
max_check_attempts 3
normal_check_interval 5
retry_check_interval 1
contact_groups MYCONTACTGROUPS
notification_interval 240
notification_period 24x7
notification_options c,r check_command check_vnc!5910 }
If you need another port than the standard one, just replace “5900”
When creating a new site, a valid certificate was issued but when expiring they where never renewed. Investigating /etc/letsencrypt directories was missing the usual subfolders, like live for example.
It turned out the server had both acme.sh and certbot installed. The solution was to remove certbot. Investigate if the directory /root/.acme.sh exists and it’s contents.
apt remove certbot
ispconfig_update.sh --forceThen in Ispconfig go to Tools -> Sync, select Web sites and the server you just removed.
It turned out the reason for this was changed permissions on the /tmp folder (caused by restoring a folder with BackupPC to /tmp instead of it’s original location).
Solution:
chown root:root /tmp
chmod 1777 /tmpAfter this apt update worked as normal.
This article will guide you to recover data on your PC when Synology NAS malfunctions.
Notes:
The drives may not be able to mount the volume again after being migrated to a new NAS.
sudo -i
apt-get update
apt-get install -y mdadm lvm2
mdadm -Asf && vgchange -ay
cat /proc/mdstat
lvs
According to the output of pvs/vgs/lvs, the device paths are as follows:
Below are the samples of md status corresponding to its RAID and volume type:
| Device Paths | Classic RAID with single volume |
| cat /proc/mdstat | root@ubuntu:~# cat /proc/mdstat Personalities : [raid1] md4 : active raid1 sdc3[0] 73328704 blocks super 1.2 [1/1] [U] unused devices:<none> |
| lvs | No output |
| ${device_path} | /dev/md4 |
| Device Paths | SHR with single volume |
| cat /proc/mdstat | root@ubuntu:~# cat /proc/mdstat Personalities : [raid1] md3 : active raid1 sda5[0] 73319616 blocks super 1.2 [1/1] [U] unused devices:<none> |
| lvs | root@ubuntu:~# lvs LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert lv vg1000 -wi-a—– 69.92g |
| ${device_path} | /dev/vg1000/lv |
| Device Paths | Classic RAID/SHR with multiple volume |
| cat /proc/mdstat | Personalities : [raid1] md3 : active raid1 sdc3[0] sdd3[1] 73328704 blocks super 1.2 [2/2] [UU] unused devices:<none> |
| lvs | root@ubuntu:~# lvs LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy% Sync Convert syno_vg_reserved_area vg1 -wi-a—– 12.00m volume_1 vg1 -wi-a—– 30.00g volume_3 vg1 -wi-a—– 30.00g |
| ${device_path} | /dev/vg1/volume_1 /dev/vg1/volume_3 |
$ mount ${device_path} ${mount_point} -o ro
If you still cannot recover the data through the above steps, refrain from trying any other methods to repair because it may cause more damage to your data. As your last option, please seek the help of a local data rescue company. Kindly understand that data retrieval is still not guaranteed.
This is beacuse mysql server 5.7 have changed the the date time default field 0000-00-00 00:00:00 options. You can only have one field with the value 0000-00-00 00:00:00. Where fore you have to change the default indata mask to.
datetime NOT NULL DEFAULT ‘1000-01-01 00:00:00’
or
timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP
exampel
ALTER TABLE testdate CHANGE datestart datestart DATETIME NOT NULL DEFAULT ‘1000-01-01 00:00:00’;
login to mysql shell as root.
locate the database where the tables are situated.
SET @DATABASE_NAME = ‘name_of_your_db’; // name_of_your_db = the database you want to change table engine.
SELECT CONCAT(‘ALTER TABLE ', table_name, ' ENGINE=InnoDB;’) AS sql_statements FROM information_schema.tables AS tb WHERE table_schema = @DATABASE_NAME AND ENGINE = ‘MyISAM’ AND TABLE_TYPE = ‘BASE TABLE’ ORDER BY table_name DESC;
The result will end up in a list of the tables that needs to be changed. Copy the list and do the following.
Shift to the database involved:
USE name_of_your_db
START TRANSACTION;
insert the copied list
COMMIT;
You have now changed the engine of the tables.
This error ocurs then the database mysql is missing or corrupt.
Stop the mysql server “service mysql-server stop”
Make a backup of /var/db/mysql “mv /var/db/mysql /var/db/mysql.old”.
To rebuild the database execute “/usr/local/libexec/mysqld –initialize”
You will get a temporary password. Remember the password for later use.
Start the mysql server “service mysql-server start”
To start upp the new configuration “mysql_secure_installation”. Use the Password to start the configuration and step thru the wizzard.
Restore the mysql backup and the server is good as new.