XOOPS 
Forum
Forum Index General Forums Community Support Modules Support Themes Support Development International Support Module Hack Reviews Theme Designer Talk
  1. Board index / 
  2. XOOPS Community Support forums / 
  3. Q and A 
  4.  / can't connect to server - what's going on?
Register
11
Eskimo-mo
Re: can't connect to server - what's going on?

  • 2008/4/2 11:54

  • Eskimo-mo

  • Just popping in

  • Posts: 22

  • Since: 2008/3/12


Hi dbman

That's done it! Thanks so much!!!

The website was actually down at the time but I could logon to the server and once I'd set up the new user and changed the mainfile the website was back up again.

So is it not a good idea to access the database using root access - was that the problem?

Thanks again
12
dbman
Re: can't connect to server - what's going on?

  • 2008/4/2 20:05

  • dbman

  • Friend of XOOPS

  • Posts: 172

  • Since: 2005/4/28


Glad to hear :)

you could have used the MySQL root user credentials in the mainfile.php but it would be not be recommended.
13
Eskimo-mo
Re: can't connect to server - what's going on?

  • 2008/4/3 9:12

  • Eskimo-mo

  • Just popping in

  • Posts: 22

  • Since: 2008/3/12


MAMA MIA!!! The problem is back (after only one day )

The server host have sent me this log to identify the problem:

Apr  3 14:23:01 njud2008 kernel: 224 pages of kernel stacks
Apr  3 14:23:05 njud2008 kernel: 0 lowmem pagetables, 2509 highmem pagetables
Apr  3 14:23:07 njud2008 kernel: 33 bounce buffer pages, 32 are on the emergency list
Apr  3 14:23:11 njud2008 kernel: Free swap:            0kB
Apr  3 14:23:18 njud2008 kernel: 261888 pages of RAM
Apr  3 14:23:20 njud2008 kernel: 32065 pages of HIGHMEM
Apr  3 14:23:21 njud2008 kernel: 6225 reserved pages
Apr  3 14:23:23 njud2008 kernel: 7359 pages shared
Apr  3 14:23:24 njud2008 kernel: 372 pages swap cached
Apr  3 14:23:25 njud2008 kernel: Out of Memory: Killed process 3456 (mysqld).
Apr  3 14:23:26 njud2008 kernel: Out of Memory: Killed process 3456 (mysqld).
Apr  3 14:23:28 njud2008 kernel: Out of Memory: Killed process 3457 (mysqld).
Apr  3 14:23:29 njud2008 kernel: Out of Memory: Killed process 3458 (mysqld).
Apr  3 14:23:30 njud2008 kernel: Out of Memory: Killed process 3459 (mysqld).
Apr  3 14:23:31 njud2008 kernel: Out of Memory: Killed process 3460 (mysqld).
Apr  3 14:23:33 njud2008 kernel: Out of Memory: Killed process 3461 (mysqld).
Apr  3 14:23:34 njud2008 kernel: Out of Memory: Killed process 3462 (mysqld).
Apr  3 14:23:35 njud2008 kernel: Out of Memory: Killed process 3463 (mysqld).
Apr  3 14:23:36 njud2008 kernel: Out of Memory: Killed process 3464 (mysqld).
Apr  3 14:23:37 njud2008 kernel: Out of Memory: Killed process 3466 (mysqld).
Apr  3 14:23:39 njud2008 kernel: Out of Memory: Killed process 3467 (mysqld).
Apr  3 14:23:41 njud2008 kernel: Out of Memory: Killed process 3468 (mysqld).
Apr  3 14:23:41 njud2008 kernel: Out of Memory: Killed process 3469 (mysqld).
Apr  3 14:23:42 njud2008 kernel: Out of Memory: Killed process 3470 (mysqld).
Apr  3 14:23:43 njud2008 kernel: Out of Memory: Killed process 3471 (mysqld).
Apr  3 14:23:43 njud2008 kernel: Out of Memory: Killed process 3472 (mysqld).
Apr  3 14:23:44 njud2008 kernel: Out of Memory: Killed process 3473 (mysqld).
Apr  3 14:23:47 njud2008 kernel: Out of Memory: Killed process 3474 (mysqld).
Apr  3 14:23:50 njud2008 kernel: Out of Memory: Killed process 3475 (mysqld).
Apr  3 14:23:52 njud2008 kernel: Out of Memory: Killed process 3476 (mysqld).
Apr  3 14:23:53 njud2008 kernel: Out of Memory: Killed process 3478 (mysqld).
Apr  3 14:23:54 njud2008 kernel: Out of Memory: Killed process 3479 (mysqld).


So something's causing me to run out of memory. my MySQL database is being killed but does that mean the problem is definitely with MySQL - how can I solve this? Any ideas??

Thanks!!!
14
avtx30
Re: can't connect to server - what's going on?

  • 2008/4/3 16:14

  • avtx30

  • Not too shy to talk

  • Posts: 181

  • Since: 2006/10/12


You said your OS was Unix didn't you? What kind of Unix? I am thinking of some problems with your kernel. Or your site is being flood
15
stefan88
Re: can't connect to server - what's going on?

  • 2008/4/3 19:53

  • stefan88

  • Community Support Member

  • Posts: 1086

  • Since: 2004/9/20


Hi,

do you use other scripts that use database?
What version of XOOPS are you using?
What settings (use custom sessions, use persistent connections ...)?
What modules/versions?

If you can, try to disable modules and enable them one by one to see where is the problem...
..
16
dbman
Re: can't connect to server - what's going on?

  • 2008/4/3 19:56

  • dbman

  • Friend of XOOPS

  • Posts: 172

  • Since: 2005/4/28


It could be your buffer or memory settings in the MySQL configuration file (my.cnf).

If you post the config settings here, as well as your unix distro and version information as avtx30 mentioned it helps troubleshoot the issue.
17
Eskimo-mo
Re: can't connect to server - what's going on?

  • 2008/4/4 7:38

  • Eskimo-mo

  • Just popping in

  • Posts: 22

  • Since: 2008/3/12


Thanks a lot for helping guys!

The server is Unix PHP 4.3.11. My XOOPS is 2.0.16

This is the my.cnf file

# Example MySQL config file for medium systems.
#
# This is for a system with little memory (32M - 64M) where MySQL plays
# an important part, or systems up to 128M where MySQL is used together with
# other programs (such as a web server)
#
# You can copy this file to
# /etc/my.cnf to set global options,
# mysql-data-dir/my.cnf to set server-specific options (in this
# installation this directory is /usr/local/mysql/data) or
# ~/.my.cnf to set user-specific options.
#
# In this file, you can use all long options that a program supports.
# If you want to know which options a program supports, run the program
# with the "--help" option.

# The following options will be passed to all MySQL clients
[client]
#password       = your_password
port            = 3306
socket          = /tmp/mysql.sock

# Here follows entries for some specific programs

# The MySQL server
[mysqld]
port            = 3306
socket          = /tmp/mysql.sock
skip-locking
key_buffer = 16M
max_allowed_packet = 1M
table_cache = 64
sort_buffer_size = 512K
net_buffer_length = 8K
myisam_sort_buffer_size = 8M

# Don't listen on a TCP/IP port at all. This can be a security enhancement,
# if all processes that need to connect to mysqld run on the same host.
# All interaction with mysqld must be made via Unix sockets or named pipes.
# Note that using this option without enabling named pipes on Windows
# (via the "enable-named-pipe" option) will render mysqld useless!
#
#skip-networking

# Replication Master Server (default)
# binary logging is required for replication
log-bin

# required unique id between 1 and 2^32 - 1
# defaults to 1 if master-host is not set
# but will not function as a master if omitted
server-id       = 1

# Replication Slave (comment out master section to use this)
#
# To configure this host as a replication slave, you can choose between
# two methods :
#
# 1) Use the CHANGE MASTER TO command (fully described in our manual) -
#    the syntax is:
#
#    CHANGE MASTER TO MASTER_HOST=, MASTER_PORT=,
#    MASTER_USER=, MASTER_PASSWORD= ;
#
#    where you replace , ,  by quoted strings and
#     by the master's port number (3306 by default).
#
#    Example:
#
#    CHANGE MASTER TO MASTER_HOST='125.564.12.1', MASTER_PORT=3306,
#    MASTER_USER='joe', MASTER_PASSWORD='secret';
#
# OR
#
# 2) Set the variables below. However, in case you choose this method, then
#    start replication for the first time (even unsuccessfully, for example
#    if you mistyped the password in master-password and the slave fails to
#    connect), the slave will create a master.info file, and any later
#    change in this file to the variables' values below will be ignored and
#    overridden by the content of the master.info file, unless you shutdown
#    the slave server, delete master.info and restart the slaver server.
#    For that reason, you may want to leave the lines below untouched
#    (commented) and instead use CHANGE MASTER TO (see above)
#
# required unique id between 2 and 2^32 - 1
# (and different from the master)
# defaults to 2 if master-host is set
# but will not function as a slave if omitted
#server-id       = 2
#
# The replication master for this slave - required
#master-host     =   
#
# The username the slave will use for authentication when connecting
# to the master - required
#master-user     =   
#
# The password the slave will authenticate with when connecting to
# the master - required
#master-password =   
#
# The port the master is listening on.
# optional - defaults to 3306
#master-port     =  
#
# binary logging - not required for slaves, but recommended
#log-bin

# Point the following paths to different dedicated disks
#tmpdir         = /tmp/
#log-update     = /path-to-dedicated-directory/hostname

# Uncomment the following if you are using BDB tables
#bdb_cache_size = 4M
#bdb_max_lock = 10000

# Uncomment the following if you are using InnoDB tables
#innodb_data_home_dir = /usr/local/mysql/data/
#innodb_data_file_path = ibdata1:10M:autoextend
#innodb_log_group_home_dir = /usr/local/mysql/data/
#innodb_log_arch_dir = /usr/local/mysql/data/
# You can set .._buffer_pool_size up to 50 - 80 %
# of RAM but beware of setting memory usage too high
#innodb_buffer_pool_size = 16M
#innodb_additional_mem_pool_size = 2M
# Set .._log_file_size to 25 % of buffer pool size
#innodb_log_file_size = 5M
#innodb_log_buffer_size = 8M
#innodb_flush_log_at_trx_commit = 1
#innodb_lock_wait_timeout = 50

[mysqldump]
quick
max_allowed_packet = 16M

[mysql]
no-auto-rehash
# Remove the next comment character if you are not familiar with SQL
#safe-updates

[isamchk]
key_buffer = 20M
sort_buffer_size = 20M
read_buffer = 2M
write_buffer = 2M

[myisamchk]
key_buffer = 20M
sort_buffer_size = 20M
read_buffer = 2M
write_buffer = 2M

[mysqlhotcopy]
interactive-timeout
[root@njud2008 data]#


It keeps going down every hour or two now!

I've tried undoing changes that I had maded recently to modules - but the problem persists
18
dbman
Re: can't connect to server - what's going on?

  • 2008/4/5 4:32

  • dbman

  • Friend of XOOPS

  • Posts: 172

  • Since: 2005/4/28


Maybe an update... I would try and move to php5 and MySQL 5. Also upgrading to XOOPS 2.0.18.1 would be a good idea.

The cnf file you are using is for generic medium memory settings. Should not be a problem if the only load on your database is your XOOPS install.

Are you running FreeBSD?
19
Eskimo-mo
Re: can't connect to server - what's going on?

  • 2008/4/7 3:06

  • Eskimo-mo

  • Just popping in

  • Posts: 22

  • Since: 2008/3/12


thanks dbman, i'll try the updates

its just unix, no freeBSD

I've just noticed in my phpMyAdmin the following messages:

Your PHP MySQL library version 3.23.49 differs from your MySQL server version 4.0.26. This may cause unpredictable behavior

and

Cannot load mcrypt extension. Please check your PHP configuration.

Is this where the problem lies? Is there a way to address these directly (as I'm a bit scared of doing a complete upgrade)
20
avtx30
Re: can't connect to server - what's going on?

  • 2008/4/7 5:30

  • avtx30

  • Not too shy to talk

  • Posts: 181

  • Since: 2006/10/12


Quote:

Your PHP MySQL library version 3.23.49 differs from your MySQL server version 4.0.26. This may cause unpredictable behavior

This caused problem I guess
« 1 (2) 3 4 »

Login

Register now!  |  Lost Password?

Search

Advanced Search

Recent Posts

Who's Online

393 user(s) are online (282 user(s) are browsing Support Forums)

Members: 0

Guests: 393

more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: Nov 30
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits