Rabu, 14 September 2011
Id "x" respawning too fast: disabled for 5 minutes
Id "x" respawning too fast: disabled for 5 minutes
I noticed this message appeared after I removed the gdm package.
To solve the above error i just disable the x:5:respawn:/etc/X11/prefdm - nodaemon
or you can set x:5:respawn:/etc/X11/prefdm - /dev/null
to test please insert telinit q to re-read the inifile
the errror message will stop.
done.
Configure SMTP mail client on Centos
modify line DAEMON=yes to DAEMON=no
save and close.
vim /etc/mail/submit.cf
modify line D{MTAhost}[127.0.0.1] to D{MTAhost}[your.smtp.ip.address]
restart sendmail service service sendmail restart
try send the email.
done.
Jumaat, 19 Ogos 2011
android
Rabu, 27 Julai 2011
Set proxy address
- login with your username
- edit .bash_profile
- Insert following line:-
http_proxy="http://yourproxyipaddress:proxyport"
export http_proxy - Done and to try out, please insert this line "elinks yahoo.com"
Disk partitioning tips
check this out..
http://www.linuxsa.org.au/tips/disk-partitioning.html
totally will help you on this!!!
Isnin, 11 Julai 2011
Acronis crontab
Selasa, 7 Jun 2011
Failover clustering in Windows Server 2008
Khamis, 12 Mei 2011
HA Cluster with Heartbeat on Centos
Keep your linux box up to date
1. Disable yum-updatesd:-
/sbin/chkconfig yum-updatesd off
2. Create yum.cron and make it executeble dan letakkan dia di folder /etc/cron.daily ataupun /etc/cron.weekly. Didalam file yum.cron itu masukan line seperti berikut:-
#!/bin/sh
/usr/bin/yum -R 120 -e 0 -d 0 -y update yum
/usr/bin/yum -R 10 -e -0 -d 0 -y update
Rabu, 23 Mac 2011
SDMC
Isnin, 28 Februari 2011
Nagios..
aku baru lepas setup nagios untuk monitor printers dan servers aku di office. Later, aku akan add kan switch, router & segala IP device yang ada dalam nagios ni.
Selasa, 22 Februari 2011
how to figure out the size in MB for an informix database
/ 1024 = Kbytes
/ 1024 = Mbytes
/ 1024 = GBytes.
Thats makes the total size of a chunk at 0.9gb
Free:
692mb
944mb
621mb
194mb
Do these numbers seem familiar? Plug them into a spread sheet for more accurate results.
Plus, be very careful when changing the disk allocations of logical volumes underneath Informix' nose. If you screw up, Informix won't like it and a level 0 archive/restore might not cut it either. Do a dbexport to disk or tape. It may take a while, and the restoration, with dbimport, may be a bit trickier with large tables. The benefit would be that the format (dbschema + unload files) is simple and does not rely on the underlying instance configuration on being exactly the same.
Rabu, 2 Februari 2011
SARG Problem
Isnin, 24 Januari 2011
SAP Administrator Daily Activities
sm51 SAP Servers
sm04/al08 Logon Users
2. Check that daily backup are executed without errors
db12 Backup logs: overview
3. SAP standard background jobs are running successfully. Review for cancelled and critical jobs.
sm37 Background jobs--- Check for successful completion of jobs. Enter * in user-id field and verify that all critical successful jobs and review any cancelled jobs.
4. Operating system Monitoring
st06
5. Extents monitoring
db02 Database monitoring--Check for max-extents reached
6. Check work-processes(started from sm51)
sm50 Process overview-- All work processes with a running or waiting status.
7. Check system log
sm21 System log-- Set date and time to before the last log review. Check for errors ,warning, security, message-bends, database events.
8. Review workload statistics
st03 Workload analysis of
sto2 tune summary instance
9. Look for any failed updates
sm13 update records
10. check for old locks
sm12 lock entry list
11. Check for spool problems
sp01 spool request screen-- check for spool that are in request for over an hour.
12. Review and resolve dumps
st22 ABAP Dump analysis
13. Checking .trc file in SAP trace directory for block corruption on daily basis.
C:\ORacle\sid\saptrace
14. Archive backup
brarchive -f force -cds -c
Insert the archive backup tape
15. Review Win system logs for problem
-> Win system log- look 4 errors or failures
-> Win security log- failed logon 2 sap servers
-> Win Application log -look 4 errors or failures
Rabu, 19 Januari 2011
Remove Squid footer completely
Isnin, 17 Januari 2011
Configuring a Standalone NtpServer
Configure a client computer for automatic domain time synchronization
Administrative Credentials
To perform this procedure, you must be a member of the Administrators group on the local computer. To perform this procedure from a remote computer, you must be a member of the Domain Admins group.
To configure a client computer for automatic domain time synchronization
Open a Command Prompt.
Type the following command and then press ENTER:
w32tm /config /syncfromflags:domhier /update
Type the following command and then press ENTER:
net stop w32time
Type the following command and then press ENTER:
net start w32time
Khamis, 13 Januari 2011
Step by step installation of the Backup Exec Remote Agent for Linux and UNIX Servers (RALUS) on the Red Hat Linux
Problem
Step by step installation of the Backup Exec Remote Agent for Linux and UNIX Servers (RALUS) on the Red Hat Linux platform.
Solution
Note: RALUS is an additionally purchased option and is enabled by installing the RALUS serial numbers on the Backup Exec media server.
It is also advisable to check the RALUS compatibility with LINUX host before installation, To check the compatibility refer to:
http://support.veritas.com/rd/bews-compatibility.htm
To install the Remote Agent for Linux and UNIX Servers on the LINUX host:
1. On a LINUX host, download the installation files from the Symantec support site.
2. Connect to the target host using a terminal session or Log On locally with super user, root, or administrator privileges.
3. Extract the contents of the installation files that were downloaded in Step 1 using the following command Figure 1a below:
Note: Do not extract the RALUS installer files on a Windows system and copy the resulting files to the Linux/Unix host. Doing so will cause difficult to diagnose installation errors. It is important to copy the .gz file to the Linux/Unix host and extract the files there as shown below.
Note: This is a one step command to extract and untar the file.
Figure 1a:
Or, in two commands as shown in Figure 1b below:
Figure 1b:
Note: This is a two step command to extract and untar the file.
4. Navigate to the Linux folder that was extracted in Step 3 as shown in Figure 2 below:
Figure 2:
5. At the command prompt, type: installralus and press
Figure 3:
6. The installation screen appears: (Figure 4)
Figure 4:
Type the LINUX server IP address or Hostname and press Enter as shown in Figure above.
7. RALUS performs the initial system check as shown in Figure 5 below:
Figure 5
Press Enter to continue.
8. RALUS will check and install the following rpms on Linux server as shown in Figure 6 below:
Figure 6:
Press Enter to continue.
9. Installation requirement checks completed successfully as shown in Figure 7 below.
Figure 7:
10. To configure RALUS with user friendly configuration press "Y" (Figure 8)
Figure 8:
11. The installation utility will now ask a series of questions to configure RALUS (Figure 9)
Figure 9:
Press Enter to continue.
12. The installation utility will ask for the Media Server IP address or Hostname to display the remote agent as a selection in the media server's backup selection tree as shown in Figure 10 below.
Note: A host name can be used, however make sure that the Linux server can resolve the host name properly. Its recommended to add the Windows host entry in the /etc/hosts file on the Linux server.
Figure 10:
13. To display the remote agent on more than one media server choose "Y" and press Enter or Simply type "N" and press Enter to continue as shown. (Figure 11)
Figure 11:
14. Confirm the Media Server IP address or Hostname by typing "Y" and press Enter, else press "N" and re-type the IP or Hostname as shown. (Figure 12)
Figure 12:
15. The installation utility will now ask to create "beoper" group as shown. (Figure 13)
Figure 13:
Note: beoper is a group that is used by Remote Agent for Linux and Unix Servers to authenticate the Backup Exec logon account, as the members of this group are given permissions to back up and restore the Linux server.
Press Enter to continue.
16. If the beoper group is not found, the installation utility will ask to create one. (Figure 14)
Figure 14:
Type "Y" and press Enter.
17. Installation utility will now prompt to specify any specific Group ID. (Figure 15)
Figure 15:
Group ID: All Linux users have a user ID and a group ID and a unique numerical identification number called a userid (UID) and a groupid (GID) respectively. Groups can be assigned to logically tie users together for a common security, privilege and access purpose. Its recommended not to assign any Group ID.
Type "N" and press Enter.
18. Note the "beoper" group has been created successfully as shown. (Figure 16)
Figure 16:
19. Installation utility will now ask to add the user root to the beoper group (Figure 17)
Figure 17:
Type "Y" and press Enter.
User root has been successfully added to the beoper group.
20. Installation utility shows successful installation of RALUS. (Figure 18)
Read the information and press Enter.
Figure 18:
21. The RALUS configuration has also completed successfully as shown. (Figure 19)
Figure 19:
Read the information and press Enter.
22. Finally, Symantec Backup Exec Remote Agent for Linux and Unix Server has completely successfully. (Figure 20)
Figure 20:
23. Reboot the server.
24. Go to the Backup Exec media server and check the remote selections listed on the Backup tab. Expand the Unix icon: (Figure 21)
Figure 21:
Utility Commands:
Use the following commands to stop and start the RALUS service as shown: (Figure 22)
Figure 22:
RALUS configuration file.
The ralus.cfg file can be edited for either troubleshooting or configuration purposes as shown.
The file is located in the following location: /etc/VRTSralus/ralus.cfg