Posts

Showing posts from June, 2021

Failed to add /run/systemd/ask-password to directory watch: No space left on device ……on your pc

  sudo -i echo 1048576 > /proc/sys/fs/inotify/max_user_watches exit

How to diagnose failed restoration attempts in JetBackup

Image
  1. Login to WHM as the root user 2. Navigate to: Home »Plugins »JetBackup 3. Click on the JetBackup icon in the upper left area to expand the side menu: 4. In the left sidebar, click on the Logs menu item 5. Locate the failed restoration from the table, and click on it to expand further options 6. Click "View Log File" 7. Review the log for further details about why the restoration failed

Roundcube webmail attach size limit

increase all php settings message_size_limit upload_max_filesize memory_limit whereis php.ini make sure there is .htaccess file in /var/www/roundcube/.htaccess i edit php ini post_max_size = 100M upload_max_filesize = 100M also /var/www/html/roundcubemail/.htaccess or comment all limitation in /var/www/html/roundcube/.htaccess #php_value   upload_max_filesize   64M #php_value   post_max_size         64M #php_value   memory_limit          64M php_value upload_max_filesize 100M php_value post_max_size 100M I need exim to allow messages larger than 20 Megabytes Last Modified: Apr 7, 2016, 9:49 pm The default setting in the /etc/exim.conf for the message size limit is: message_size_limit = 20M You can edit the /etc/exim.conf and increase this value as needed.  Restart exim after changing the value /etc/init.d/exim restart SpamBlocker 4.x+ Newer exim.conf versions will use the /etc/exim.variables.conf file. To change that, edit /etc/exim.variables.conf.custom using the  custom variables gui

zimbra restore bckup from file system /opt/zimbra

$ zmprov getMailboxInfo b@test.test mailboxId: 16 quotaUsed: 1951021 [zimbra@mail root]$ zmprov getMailboxInfo hgarware@gartech.co.in mailboxId: 16 quotaUsed: 40745785417 /backup3/allbackup/INDIA/192.227.91.253/DAILY/opt/zimbra/store/0/16/msg /opt/zimbra/bin/zmmailbox -z -m  d.niin@drushti.in addMessage /Recovery(DirectoryName were u want to restore emails) /backup/opt/zimbra/store/0/32/msg/0/* /opt/zimbra/bin/zmmailbox -z -m  hgarware@gartech.co.in addMessage /allmails /mnt/hgarware/* here allmails is the directory that you need to create in the mail is from view emails outside of inbox check all folder mail will be stored in date wise do ll and check mysql -e "select email,mailbox_id from zimbra.deleted_account" mysql -e "select email,mailbox_id from zimbra.deleted_account" +------------------------------+------------+ | email                        | mailbox_id | +------------------------------+------------+ | amol@fristam.in              |         16 | | demo@zi

ERROR: zclient.UPLOAD_SIZE_LIMIT_EXCEEDED (upload size limit exceeded)

 [zimbra@mail hgarware]$ zmprov gcf zimbraMailContentMaxSize zimbraMailContentMaxSize: 102400000 zmprov mcf zimbraFileUploadMaxSize 90000000000000 zmprov mcf zimbraFileUploadMaxSize 40000000 zmprov mcf zimbraFileUploadMaxSizePerFile 2147483648 zmprov mcf zimbraMtaMaxMessageSize 40000000 zmprov mcf zimbraMailContentMaxSize 102400000

zimbra high security

 home>configure>class of service

Apache 2.4 Failed To Start AH00016: Configuration Failed

  Apache 2.4 Failed To Start AH00016: Configuration Failed   October 5, 2014     james     Apache ,  Ubuntu Server One of our Apache 2.4 web servers strangely stopped working and didn’t want to come back up. I tried to start it but it came back with a vague error message: $ sudo service apache2 start Starting web server apache2 Action 'start' failed. The Apache error log may have more information. A quick look in /var/log/apache2/error.log just showed nothing useful: $ tail var/log/apache2/error.log AH00016: Configuration Failed, exiting So, I ran the Apache configuration check tool on the configuration files but the syntax was okay. $ sudo apache2ctl configtest Syntax OK This means that there isn’t anything wrong with the syntax of the Apache config and I generally find that this means either an SSL certificate isn’t installed incorrectly or there is something wrong with a more general configuration file. To find which host had configuration file problems – I used the  strace