cd /opt/casp enter
service asp-server-3000 status enter
(if server status is stopped then )
service asp-server-3000 start enter
(else)
service asp-server-3000 restart enter
1. Edit /etc/exim.conf
2. On the second line add :
log_selector = +address_rewrite +all_parents +arguments +connection_reject +delay_delivery +delivery_size +dnslist_defer +incoming_interface +incoming_port +lost_incoming_connection +queue_run +received_sender +received_recipients +retry_defer +sender_on_delivery +size_reject +skip_delivery +smtp_confirmation +smtp_connection +smtp_protocol_error +smtp_syntax_error +subject +tls_cipher +tls_peerdn \
Make sure all that comes on a single line.
3. Save and exit.
4. Restart Exim.
A little bit luck and you should be able to catch the spammer.
sh install_formmail_trap
go to /var/log
# tail -f formmail.log
———————————————-
If you want to reset quota , execute the following command on the control panel server by executing as root:
# su – cpanel -c “java psoft.hsphere.tools.SetQuota”
This will reset quota for all users on the system on all servers, so it might take quite a while to execute.
[COLOR=red]Please note that since this is going to reset the quota for all the users , make sure that you consult some senior person before attempting this.
$ /etc/rc.d/init.d/httpdcp stop
$ sleep 10
$ /etc/rc.d/init.d/httpdcp start
Normally after restarting the CP the error is fixed , but even after
restarting the control panel the error is not fixed then possibly your
PostgreSQL database is down.
you can start the postgreSql using the following command,
$ /etc/init.d/rc.d/postgresql restart
restart control panel after this and the ” 500 internal server error ” will
vanish.
How to Add a new Server in Hsphere?
Following is procedure to add a new server to the control panel :Add a physical server first ,following is the procedure to add a physical server,
1)In the admin control panel, select Add P. Server in the E.Manager menu.
2)Click Add Physical Server at the bottom of the page that appears.
3)On the next page, enter the name of the physical server, its IP and associated mask. For windows server, also enter a login and password you chose when installing the Win box.
Note : Don’t enter IP2 and Mask2, they are not implemented for Linux and for Windows.
4)At the bottom of the next page, select the group (type) of logical servers to be placed on this physical server.
E.g.: If you add only web servers and mail servers, you won’t be able to add a DNS server to this physical server in the future.
Note: Win, Win Real and MS SQL server groups are not compatible with other groups, and each of them requires a separate physical server.
5)Select Add P.Server in the E.Manager menu to see the newly added server in the list of all physical servers in the system.
After this you will need to add the logical server,
To add a new logical server to H-Sphere, do the following:
1)Go to your admin control panel.
2)Click Add L.Server in the E.Manager menu.
3)On the page that appears, enter the properties of the logical server:
Name: The domain name of the logical server;
Group: The group of logical servers you are adding this server to.
Type: The type of the server.Physical Server: The box where the logical server is installed. If nothing is available in the dropdown box, add this server group to the physical server first.
Description: The note that will help you identify this server among others.
File Server: Reserved for future implementation.
File Path: Reserved for future implementation.
4)Add DNS records for this logical server, as suggested in the DNS Configuration guide.
5)If you are adding a web server, select Shared SSL Manager in the E.Manager menu, click the Edit icon next to the domain name and enter the certificate key and certificate file in the Install completely new certificate key and file pair boxes. Then click the Upload button. This will update the shared SSL certificate installation on all servers, including the newly installed one
then do as follows:
rm -f /usr/local/psa/var/webalizer.cache
touch /usr/local/psa/var/webalizer.cache
chown root:root /usr/local/psa/var/webalizer.cache
chmod 644 /usr/local/psa/var/webalizer.cache
stat /usr/local/psa/var/webalizer.cache
* Other qmail tips and tools are available at http://www.qmail.org/top.html . Also provided here are links to searchable archives of the qmail mailing list.
* To see how many messages are currently in the queue, use /var/qmail/bin/qmail-qstat (/usr/local/psa/qmail/bin/qmail-qstat on Plesk 2.5 servers).
* For more detailed information about the messages currently in the queue, use /var/qmail/bin/qmail-qread (/usr/local/psa/qmail/bin/qmail-qread on Plesk 2.5 servers). This command is similar to the sendmail mailq command.
* qmail’s configuration files are kept in /var/qmail/control (or /usr/local/psa/qmail/control). Together these files are equivalent to the sendmail.cf file (but much easier to read IMNSHO). LWQ provides an explanation of what each of these files is for, and so does “man qmail-control”. You may need to add the qmail man directory to the MANPATH environment variable for this man page to be found; if so, the directory is usually /var/qmail/man.
* The qmail queue directory is typically /var/qmail/queue (or /usr/local/psa/qmail/queue). Do NOT manipulate the files in this directory UNLESS you know exactly what you are doing, and UNLESS qmail is not running! Otherwise, you WILL break the queue! There are several programs listed at qmail.org designed to allow safe manipulation of the queue. In particular, Charles Cazabon, the author of memtester, has also written a qmail queue repair program, available at http://www.qcc.ca/~charlesc/software/queue_repair/ .
* Cazabon’s queue_repair program is particularly handy for wiping out qmail queues of servers being abused by spammers (usually courtesy of Plesk’s “open relay” option). The general steps are: stop qmail, move or delete the queue directory, run queue_repair with the appropriate options, then restart qmail. On Plesk 5 and 6 servers, the queue directory is /var/qmail/queue and qmail_repair should be run like so: “qmail_repair.py -c -s 23 -b”. For other servers, the queue directory will most likely be /var/qmail/queue (/usr/local/psa/qmail/queue for Plesk 2.5 servers), and qmail_repair will be run as either “qmail_repair.py -c -s XX -b /path/to/queue” or “qmail_repair.py -c -s XX -n /path/to/queue”. XX is the number of subdirectories within the queue’s info and mess directories; the “-b” option is used if there are subdirectories within the queue’s todo directory, and the “-n” option is used otherwise; “/path/to/queue” is optional if the queue directory is /var/qmail/queue.
2. Right Click on the server name (the second tab in IIS manager screen)
3. Go to All Tasks – Backup and Restore – Create – Type the name of backups here (preferably a dated name) – start
This will take a few minutes depending on the number of sites on the server.
4. Once this is complete, you can go ahead with the uninstall and re-install without any doubts.Restoring a backup
1. Open IIS manager
2. Right Click on the server name (the second tab in IIS manager screen)
3. Go to All Tasks – Backup and Restore – Select the backup you created in the above process – Restore
It will again take quite a while to complete the restore process.
4. Once done, you may require to restart IIS (not always but it does become neccessary sometimes). do it as follows:
go to comand prompt, and type iisreset /restart
5. Thats it, you can see all the original sites and configuratiosn backonline without problems.
The Windows section of the forum needs some work considering the fact that we operate on both Linux and Windows servers, ofcourse compensating for the number difference among them.
Hence I would like to take the opportunity presented by the forum to start a topic on Security in IIS. I hope it interests all of you enough to put in some postings of your own.
Lets Start with the simplest of things to be undertaken to implement a secure Site in IIS
1. Configure IPSec Policy
2. Secure the Telnet Server
3. Disable NetBIOS over TCP/IP
4. Use the security template Hisecweb.inf to configure basic Windows 2000 systemwide policy. Hisecweb.inf template is used as a baseline applicable to most secure Web sites.
Ofcourse, due considerations need to be given to the functionality and security issues. This is important as with an increase in security, there is a corresponding decrease in functionality. These issues should be sorted and chalked out before any security arrangement is implemented.