Sponsored Content
Operating Systems Linux Red Hat postgresql issues - system running really slow Post 302275831 by clive306 on Monday 12th of January 2009 09:40:27 AM
Old 01-12-2009
postgresql issues - system running really slow

Hi All,

I'm new here.

i was wondering if anyone could shed a light on the problem i am having.
I use a system for distributing broadband amongst users of for example a hotel, the system was designed by someone in the US and it is based on redhat 2.4 (i know its old) and the system uses Postgresl NOT mysql.

the problem i am having is that i cannot contact the company for linux support no more and the system itself is failing fast. the problem is speed. its really slow at performing database request, in some cases so slow that it just doesn't work at all.

I have a script on the system calles auto_vacumm for postgresql and it is setup in crontab to run daily, but this seems to make no difference to the performance of the server.

could anyone point me in the right direction to solving the problem, i have checked 'top' and the CPU is running @ 90%+ idle.

any information would be very much appreciated.

thanks in advance
Clive.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Slow System

Hi, I have an SCO-Unix server running. There are some processes (unknown to me) which consume a lot of the system resources. This slows down the server dramatically. Is there a command or program that monitors what processes are using the cpu, disk, etc.. and tell me how excessive and how... (3 Replies)
Discussion started by: Hansaplast
3 Replies

2. Solaris

Solaris running very slow!!

Hi all, Solaris is working very slow as login to solaris takes time say after 10 to 15 mins we get the login prompt back after logging in as oracle account/other account. This causes most Batch run delays(DWHouse jobs) scheduled through cronjobs. Where should one look for such issues to... (3 Replies)
Discussion started by: a1_win
3 Replies

3. SCO

Server running slow

Hi, Wonder is someone can help. I've got a server SCO_SV 3.2v5.0.7 PentIII that is located at a different site and is running slow and has been for a week. I've been speaking to a third party who say nothing is wrong with it but its still running slow. The 3rd party advise it could be a... (2 Replies)
Discussion started by: tez
2 Replies

4. HP-UX

SAM running slow

Any ideas on why SAM would take so long to load and initialize? (4 Replies)
Discussion started by: csaunders
4 Replies

5. UNIX for Dummies Questions & Answers

Unix is running slow??

All, This is my interview questions. Let me explain the question. Some one is asking me that, the unix server is running very slow. As a unix unix admin, what are the steps we should follow?? What/which process we should check?? What is the way to find the root cause ? Please let me know.... (8 Replies)
Discussion started by: govindts
8 Replies

6. Solaris

Slow while running a command for the first time

I am facing a performance problem on a Solaris 10 Sparc V890 server, it is an old one I know. The first time we realized there is a problem with the server, is the time when ftp transfers are made. There were 4 other identical servers doing much better. Network drivers are checked and there... (3 Replies)
Discussion started by: royalliege
3 Replies

7. UNIX for Dummies Questions & Answers

swap issues, system is running at 99%

Hi All, I am trying to understand why my system is running at very high. This system is almost out of memory. See below. swapon -s Filename Type Size Used Priority /dev/mapper/VolGroup00-LogVol02 partition 8388600 8235088 -1... (2 Replies)
Discussion started by: samnyc
2 Replies

8. UNIX for Dummies Questions & Answers

Ubuntu seems running slow!

Hello, My PC seems running slow: OS32 system, Pentium(R)4---2.40Ghz, 1GB RAM, 80GB HDI am running Ubuntu 11.10 (Oneiric Ocelot) alone in this box, which seems very slow to me. Is this normal? Compared with my other PC (Running XP) with 1.99GHz AMD Athlon 3200+, 2GB RAM,500GB HD, XP and Mint... (11 Replies)
Discussion started by: yifangt
11 Replies

9. Shell Programming and Scripting

Slow Running Script (Reading 8000 lines)

Slow runnin script. The problem seems to be the sed calls. In summary the script reads list of users in file1. For each username search two files (file 1 & file2) for the username and get the value in the next line after "=". Compare these values with each other. If the same then output... (9 Replies)
Discussion started by: u20sr
9 Replies

10. AIX

AIX server running very slow

Hello, All the commands on AIX are running very slow. Below is few stats but I didn't find any issue in cpu or memory reosurces vmstat System configuration: lcpu=4 mem=6144MB ent=1.00 kthr memory page faults cpu ----- -----------... (2 Replies)
Discussion started by: Vishal_dba
2 Replies
postgresql_selinux(8)					     SELinux Policy postgresql					     postgresql_selinux(8)

NAME
postgresql_selinux - Security Enhanced Linux Policy for the postgresql processes DESCRIPTION
Security-Enhanced Linux secures the postgresql processes via flexible mandatory access control. The postgresql processes execute with the postgresql_t SELinux type. You can check if you have these processes running by executing the ps command with the -Z qualifier. For example: ps -eZ | grep postgresql_t ENTRYPOINTS
The postgresql_t SELinux type can be entered via the postgresql_exec_t file type. The default entrypoint paths for the postgresql_t domain are the following: /usr/bin/(se)?postgres, /usr/bin/initdb(.sepgsql)?, /usr/lib/postgresql/bin/.*, /usr/bin/pg_ctl, /usr/lib/pgsql/test/regress/pg_regress PROCESS TYPES
SELinux defines process types (domains) for each process running on the system You can see the context of a process using the -Z option to ps Policy governs the access confined processes have to files. SELinux postgresql policy is very flexible allowing users to setup their post- gresql processes in as secure a method as possible. The following process types are defined for postgresql: postgresql_t Note: semanage permissive -a postgresql_t can be used to make the process type postgresql_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. BOOLEANS
SELinux policy is customizable based on least access required. postgresql policy is extremely flexible and has several booleans that allow you to manipulate the policy and run postgresql with the tightest access possible. If you want to allow postgresql to use ssh and rsync for point-in-time recovery, you must turn on the postgresql_can_rsync boolean. Dis- abled by default. setsebool -P postgresql_can_rsync 1 If you want to allow transmit client label to foreign database, you must turn on the postgresql_selinux_transmit_client_label boolean. Dis- abled by default. setsebool -P postgresql_selinux_transmit_client_label 1 If you want to allow users to resolve user passwd entries directly from ldap rather then using a sssd server, you must turn on the authlo- gin_nsswitch_use_ldap boolean. Disabled by default. setsebool -P authlogin_nsswitch_use_ldap 1 If you want to allow all daemons to write corefiles to /, you must turn on the daemons_dump_core boolean. Disabled by default. setsebool -P daemons_dump_core 1 If you want to enable cluster mode for daemons, you must turn on the daemons_enable_cluster_mode boolean. Enabled by default. setsebool -P daemons_enable_cluster_mode 1 If you want to allow all daemons to use tcp wrappers, you must turn on the daemons_use_tcp_wrapper boolean. Disabled by default. setsebool -P daemons_use_tcp_wrapper 1 If you want to allow all daemons the ability to read/write terminals, you must turn on the daemons_use_tty boolean. Disabled by default. setsebool -P daemons_use_tty 1 If you want to deny user domains applications to map a memory region as both executable and writable, this is dangerous and the executable should be reported in bugzilla, you must turn on the deny_execmem boolean. Enabled by default. setsebool -P deny_execmem 1 If you want to deny any process from ptracing or debugging any other processes, you must turn on the deny_ptrace boolean. Enabled by default. setsebool -P deny_ptrace 1 If you want to allow all domains to use other domains file descriptors, you must turn on the domain_fd_use boolean. Enabled by default. setsebool -P domain_fd_use 1 If you want to allow all domains to have the kernel load modules, you must turn on the domain_kernel_load_modules boolean. Disabled by default. setsebool -P domain_kernel_load_modules 1 If you want to determine whether exim can connect to databases, you must turn on the exim_can_connect_db boolean. Disabled by default. setsebool -P exim_can_connect_db 1 If you want to allow all domains to execute in fips_mode, you must turn on the fips_mode boolean. Enabled by default. setsebool -P fips_mode 1 If you want to determine whether ftpd can connect to databases over the TCP network, you must turn on the ftpd_connect_db boolean. Disabled by default. setsebool -P ftpd_connect_db 1 If you want to enable reading of urandom for all domains, you must turn on the global_ssp boolean. Disabled by default. setsebool -P global_ssp 1 If you want to allow HTTPD scripts and modules to connect to databases over the network, you must turn on the httpd_can_network_connect_db boolean. Disabled by default. setsebool -P httpd_can_network_connect_db 1 If you want to allow confined applications to run with kerberos, you must turn on the kerberos_enabled boolean. Enabled by default. setsebool -P kerberos_enabled 1 If you want to allow system to run with NIS, you must turn on the nis_enabled boolean. Disabled by default. setsebool -P nis_enabled 1 If you want to allow confined applications to use nscd shared memory, you must turn on the nscd_use_shm boolean. Enabled by default. setsebool -P nscd_use_shm 1 If you want to allow users to connect to PostgreSQL, you must turn on the selinuxuser_postgresql_connect_enabled boolean. Disabled by default. setsebool -P selinuxuser_postgresql_connect_enabled 1 NSSWITCH DOMAIN
If you want to allow users to resolve user passwd entries directly from ldap rather then using a sssd server for the postgresql_t, you must turn on the authlogin_nsswitch_use_ldap boolean. setsebool -P authlogin_nsswitch_use_ldap 1 If you want to allow confined applications to run with kerberos for the postgresql_t, you must turn on the kerberos_enabled boolean. setsebool -P kerberos_enabled 1 PORT TYPES
SELinux defines port types to represent TCP and UDP ports. You can see the types associated with a port by using the following command: semanage port -l Policy governs the access confined processes have to these ports. SELinux postgresql policy is very flexible allowing users to setup their postgresql processes in as secure a method as possible. The following port types are defined for postgresql: postgresql_port_t Default Defined Ports: tcp 5432 MANAGED FILES
The SELinux process type postgresql_t can manage files labeled with the following file types. The paths listed are the default paths for these file types. Note the processes UID still need to have DAC permissions. cluster_conf_t /etc/cluster(/.*)? cluster_var_lib_t /var/lib/pcsd(/.*)? /var/lib/cluster(/.*)? /var/lib/openais(/.*)? /var/lib/pengine(/.*)? /var/lib/corosync(/.*)? /usr/lib/heartbeat(/.*)? /var/lib/heartbeat(/.*)? /var/lib/pacemaker(/.*)? cluster_var_run_t /var/run/crm(/.*)? /var/run/cman_.* /var/run/rsctmp(/.*)? /var/run/aisexec.* /var/run/heartbeat(/.*)? /var/run/cpglockd.pid /var/run/corosync.pid /var/run/rgmanager.pid /var/run/cluster/rgmanager.sk faillog_t /var/log/btmp.* /var/log/faillog.* /var/log/tallylog.* /var/run/faillock(/.*)? hugetlbfs_t /dev/hugepages /lib/udev/devices/hugepages /usr/lib/udev/devices/hugepages krb5_host_rcache_t /var/cache/krb5rcache(/.*)? /var/tmp/nfs_0 /var/tmp/DNS_25 /var/tmp/host_0 /var/tmp/imap_0 /var/tmp/HTTP_23 /var/tmp/HTTP_48 /var/tmp/ldap_55 /var/tmp/ldap_487 /var/tmp/ldapmap1_0 lastlog_t /var/log/lastlog.* postgresql_db_t /var/lib/pgsql(/.*)? /var/lib/sepgsql(/.*)? /var/lib/postgres(ql)?(/.*)? /usr/share/jonas/pgsql(/.*)? /usr/lib/pgsql/test/regress(/.*)? postgresql_lock_t postgresql_log_t /var/lib/pgsql/.*.log /var/log/rhdb/rhdb(/.*)? /var/log/postgresql(/.*)? /var/log/postgres.log.* /var/lib/pgsql/logfile(/.*)? /var/log/sepostgresql.log.* /var/lib/pgsql/data/pg_log(/.*)? /var/lib/sepgsql/pgstartup.log postgresql_tmp_t postgresql_var_run_t /var/run/postgresql(/.*)? root_t / /initrd security_t /selinux FILE CONTEXTS
SELinux requires files to have an extended attribute to define the file type. You can see the context of a file using the -Z option to ls Policy governs the access confined processes have to these files. SELinux postgresql policy is very flexible allowing users to setup their postgresql processes in as secure a method as possible. EQUIVALENCE DIRECTORIES postgresql policy stores data with multiple different file context types under the /var/lib/sepgsql directory. If you would like to store the data in a different directory you can use the semanage command to create an equivalence mapping. If you wanted to store this data under the /srv dirctory you would execute the following command: semanage fcontext -a -e /var/lib/sepgsql /srv/sepgsql restorecon -R -v /srv/sepgsql postgresql policy stores data with multiple different file context types under the /var/lib/pgsql directory. If you would like to store the data in a different directory you can use the semanage command to create an equivalence mapping. If you wanted to store this data under the /srv dirctory you would execute the following command: semanage fcontext -a -e /var/lib/pgsql /srv/pgsql restorecon -R -v /srv/pgsql STANDARD FILE CONTEXT SELinux defines the file context types for the postgresql, if you wanted to store files with these types in a diffent paths, you need to execute the semanage command to sepecify alternate labeling and then use restorecon to put the labels on disk. semanage fcontext -a -t postgresql_db_t '/srv/postgresql/content(/.*)?' restorecon -R -v /srv/mypostgresql_content Note: SELinux often uses regular expressions to specify labels that match multiple files. The following file types are defined for postgresql: postgresql_db_t - Set files with the postgresql_db_t type, if you want to treat the files as postgresql database content. Paths: /var/lib/pgsql(/.*)?, /var/lib/sepgsql(/.*)?, /var/lib/postgres(ql)?(/.*)?, /usr/share/jonas/pgsql(/.*)?, /usr/lib/pgsql/test/regress(/.*)? postgresql_etc_t - Set files with the postgresql_etc_t type, if you want to store postgresql files in the /etc directories. Paths: /etc/postgresql(/.*)?, /etc/sysconfig/pgsql(/.*)? postgresql_exec_t - Set files with the postgresql_exec_t type, if you want to transition an executable to the postgresql_t domain. Paths: /usr/bin/(se)?postgres, /usr/bin/initdb(.sepgsql)?, /usr/lib/postgresql/bin/.*, /usr/bin/pg_ctl, /usr/lib/pgsql/test/regress/pg_regress postgresql_initrc_exec_t - Set files with the postgresql_initrc_exec_t type, if you want to transition an executable to the postgresql_initrc_t domain. postgresql_lock_t - Set files with the postgresql_lock_t type, if you want to treat the files as postgresql lock data, stored under the /var/lock directory postgresql_log_t - Set files with the postgresql_log_t type, if you want to treat the data as postgresql log data, usually stored under the /var/log direc- tory. Paths: /var/lib/pgsql/.*.log, /var/log/rhdb/rhdb(/.*)?, /var/log/postgresql(/.*)?, /var/log/postgres.log.*, /var/lib/pgsql/logfile(/.*)?, /var/log/sepostgresql.log.*, /var/lib/pgsql/data/pg_log(/.*)?, /var/lib/sepgsql/pgstartup.log postgresql_tmp_t - Set files with the postgresql_tmp_t type, if you want to store postgresql temporary files in the /tmp directories. postgresql_var_run_t - Set files with the postgresql_var_run_t type, if you want to store the postgresql files under the /run or /var/run directory. Note: File context can be temporarily modified with the chcon command. If you want to permanently change the file context you need to use the semanage fcontext command. This will modify the SELinux labeling database. You will need to use restorecon to apply the labels. COMMANDS
semanage fcontext can also be used to manipulate default file context mappings. semanage permissive can also be used to manipulate whether or not a process type is permissive. semanage module can also be used to enable/disable/install/remove policy modules. semanage port can also be used to manipulate the port definitions semanage boolean can also be used to manipulate the booleans system-config-selinux is a GUI tool available to customize SELinux policy settings. AUTHOR
This manual page was auto-generated using sepolicy manpage . SEE ALSO
selinux(8), postgresql(8), semanage(8), restorecon(8), chcon(1), sepolicy(8) , setsebool(8) postgresql 14-06-10 postgresql_selinux(8)
All times are GMT -4. The time now is 11:28 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy