Koozali.org: home of the SME Server

Howto create full backup on Sme server 7.0

lars2670

Howto create full backup on Sme server 7.0
« on: December 25, 2006, 11:12:00 AM »
hallo.

My SME server 7.0 can`t create a full backup from the Server-manager - Backup and Restore Why ?

I haft change my mysql Root user password and efter this can`t create this backup to desktop.


Operation status report
Error occurred during pre-backup actions


Plzz help my :)

Thank you.

Offline TheMonk

  • *
  • 14
  • +0/-0
Re: Howto create full backup on Sme server 7.0
« Reply #1 on: December 25, 2006, 05:57:15 PM »
Hi Lars! (2670=Greve?)

Quote from: "lars2670"

My SME server 7.0 can`t create a full backup from the Server-manager - Backup and Restore Why ?

I haft change my mysql Root user password and efter this can`t create this backup to desktop.


This message might help you...   :wink:

...or maybe this message is even better

Note you can not take a full backup using the backup to desktop function; only your 'data' will be backed up
......

Offline pfloor

  • *****
  • 889
  • +1/-0
Re: Howto create full backup on Sme server 7.0
« Reply #2 on: December 26, 2006, 05:59:00 PM »
Quote from: "TheMonk"
Hi Lars! (2670=Greve?)

Quote from: "lars2670"

My SME server 7.0 can`t create a full backup from the Server-manager - Backup and Restore Why ?

I haft change my mysql Root user password and efter this can`t create this backup to desktop.


This message might help you...   :wink:

...or maybe this message is even better

Note you can not take a full backup using the backup to desktop function; only your 'data' will be backed up


Neither of those topics will help.  Neither have the correct procedure to reset the mysql root password in SME7. The correct procedure is

Code: [Select]

# cd /var/service/mysqld
# runsvctrl d .
# expand-template /root/.my.cnf
# expand-template /var/service/mysqld/set.password
# /usr/libexec/mysqld --bootstrap --user=mysql --skip-grant-tables < ./set.password
# runsvctrl u .


Look here for more background: http://bugs.contribs.org/show_bug.cgi?id=778

As has been said MANY MANY times...

NEVER, EVER UNDER ANY CONDITIONS CHANGE THE MYSQL ROOT PASSWORD...EVER!!!
In life, you must either "Push, Pull or Get out of the way!"

oliwbol

Same issue
« Reply #3 on: January 18, 2007, 02:40:21 AM »
Hello all,

I have a simular issue, I am unable to run a ‘backup to desktop’ on my SME server 7.1, as I also get the “Error occurred during pre-backup actions.” error

I have read trough all of the articles that are linked to this message and I have not had much success.

Well I did change the MYSQL root password, and I promise that I will never ever ever do it again… promise.  However I reset the root password in MySQLadmin prompt to what it was at install ‘’(null) this did not work so  I also tryed the code provided by monk

# cd /var/service/mysqld
# runsvctrl d .
# expand-template /root/.my.cnf
# expand-template /var/service/mysqld/set.password
# /usr/libexec/mysqld --bootstrap --user=mysql --skip-grant-tables < ./set.password
# runsvctrl u .

Unfortunately this has not really helped at all as I still get the same errors. So over to the brains trust :-) what should i do next

any help would be great, cheers

olie

oliwbol

Howto create full backup on Sme server 7.0
« Reply #4 on: January 18, 2007, 02:46:42 AM »
sorry i meant pfloor not monk .... sorry pfloor

Offline pfloor

  • *****
  • 889
  • +1/-0
Re: Same issue
« Reply #5 on: January 18, 2007, 03:07:31 AM »
Quote from: "oliwbol"
Hello all,

I have a simular issue, I am unable to run a ‘backup to desktop’ on my SME server 7.1, as I also get the “Error occurred during pre-backup actions.” error

There are only 3 events in the pre-backup action.

1-Deletes any previous mysql.dump.
2-Creates a new mysql.dump
3-Rewinds the tape drive (if you have one).

You need to look in your log file and get the exact error form the time of the attemped backup and post them here.

Quote from: "oliwbol"
I have read trough all of the articles that are linked to this message and I have not had much success.

Well I did change the MYSQL root password, and I promise that I will never ever ever do it again… promise.  However I reset the root password in MySQLadmin prompt to what it was at install ‘’(null)


The mysql root password was never null.  It wa a specially assigned 76 char high security password.  There is a mechanism that allow you to access mysql if you are logged in as root without having to know the 76 char password.

Quote from: "oliwbol"
this did not work so  I also tryed the code provided by monk

# cd /var/service/mysqld
# runsvctrl d .
# expand-template /root/.my.cnf
# expand-template /var/service/mysqld/set.password
# /usr/libexec/mysqld --bootstrap --user=mysql --skip-grant-tables < ./set.password
# runsvctrl u .

Unfortunately this has not really helped at all as I still get the same errors. So over to the brains trust :-) what should i do next

any help would be great, cheers

olie

Your commands look correct. Did you get any errors when executing them?
In life, you must either "Push, Pull or Get out of the way!"

oliwbol

Howto create full backup on Sme server 7.0
« Reply #6 on: January 18, 2007, 05:37:35 AM »
1. sorry i assumed that the root pwd was null as when i did the
# mysql -u root -p i would let me straight in ?

2. sorry to be a newbie but where does the particular log file live?

oliwbol

Howto create full backup on Sme server 7.0
« Reply #7 on: January 18, 2007, 06:48:31 AM »
MYSQL Current Log:
2007-01-18 08:50:22.769811500 /usr/libexec/mysqld: ready for connections.
2007-01-18 08:50:22.769818500 Version: '4.1.20'  socket: '/var/lib/mysql/mysql.sock'  port: 0  Source distribution
2007-01-18 10:25:34.745620500 /usr/libexec/mysqld: ready for connections.
2007-01-18 10:25:34.745627500 Version: '4.1.20'  socket: '/var/lib/mysql/mysql.sock'  port: 0  Source distribution
2007-01-18 10:38:43.832621500 070118 10:38:43 [Note] /usr/libexec/mysqld: Normal shutdown
2007-01-18 10:38:43.832628500
2007-01-18 10:38:43.834106500 070118 10:38:43 [Note] /usr/libexec/mysqld: Shutdown complete
2007-01-18 10:38:43.834111500

the MYSQLD log is empty :-

anything Else i need to look at

Offline pfloor

  • *****
  • 889
  • +1/-0
Howto create full backup on Sme server 7.0
« Reply #8 on: January 18, 2007, 05:27:02 PM »
Look at your "messages" log around the time of the failed backup attempt.
In life, you must either "Push, Pull or Get out of the way!"

oliwbol

Howto create full backup on Sme server 7.0
« Reply #9 on: January 19, 2007, 12:01:50 AM »
cheers mate

Wow strange days indeed, I got in this morning and found that the server had hung, for some strange reason.  Below is the messages log file.  But the backup process is working. I would still like to know what stoped it from going though;

------------------
Failed Backup
------------------
Jan 18 13:28:04 catimor HORDE[3899]: [horde] DB Error: connect failed:  [nativecode=Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)] ** Array [on line 1624 of "/home/httpd/html/horde/lib/Horde/DataTree/sql.php"]
Jan 18 15:37:23 catimor smbd[4337]: [2007/01/18 15:37:23, 0] lib/util_sock.c:read_socket_data(384)
Jan 18 15:37:23 catimor smbd[4337]:   read_socket_data: recv failure for 4. Error = No route to host
Jan 18 15:40:00 catimor /etc/e-smith/web/panels/manager/cgi-bin/backup[4773]: /home/e-smith/db/backups: OLD 1169098800=(undefined)
Jan 18 15:40:00 catimor /etc/e-smith/web/panels/manager/cgi-bin/backup[4773]: /home/e-smith/db/backups: NEW 1169098800=backup_record|BackupType|desktop|StartEpochTime|1169098800
Jan 18 15:40:00 catimor esmith::event[4774]: Processing event: pre-backup desktop
Jan 18 15:40:00 catimor esmith::event[4774]: Running event handler: /etc/e-smith/events/pre-backup/S10mysql-delete-dumped-tables
Jan 18 15:40:00 catimor esmith::event[4774]: S10mysql-delete-dumped-tables=action|Event|pre-backup|Action|S10mysql-delete-dumped-tables|Start|1169098800 893840|End|1169098800 898579|Elapsed|0.004739
Jan 18 15:40:00 catimor esmith::event[4774]: Running event handler: /etc/e-smith/events/pre-backup/S20mysql-dump-tables
Jan 18 15:40:01 catimor esmith::event[4774]: mysqldump: Got error: 2002: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2) when trying to connect  
Jan 18 15:40:01 catimor esmith::event[4774]: S20mysql-dump-tables=action|Event|pre-backup|Action|S20mysql-dump-tables|Start|1169098800 899301|End|1169098801 7627|Elapsed|0.108326|Status|512
Jan 18 15:40:01 catimor esmith::event[4774]: Running event handler: /etc/e-smith/events/pre-backup/S50rewind-tape
Jan 18 15:40:01 catimor esmith::event[4774]: S50rewind-tape=action|Event|pre-backup|Action|S50rewind-tape|Start|1169098801 8026|End|1169098801 199748|Elapsed|0.191722
Jan 18 15:40:01 catimor /etc/e-smith/web/panels/manager/cgi-bin/backup[4773]: /home/e-smith/db/backups: OLD 1169098800=backup_record|BackupType|desktop|StartEpochTime|1169098800
Jan 18 15:40:01 catimor /etc/e-smith/web/panels/manager/cgi-bin/backup[4773]: /home/e-smith/db/backups: NEW 1169098800=backup_record|BackupType|desktop|EndEpochTime|1169098801|StartEpochTime|1169098800
Jan 18 15:40:01 catimor /etc/e-smith/web/panels/manager/cgi-bin/backup[4773]: /home/e-smith/db/backups: OLD 1169098800=backup_record|BackupType|desktop|EndEpochTime|1169098801|StartEpochTime|1169098800
Jan 18 15:40:01 catimor /etc/e-smith/web/panels/manager/cgi-bin/backup[4773]: /home/e-smith/db/backups: NEW 1169098800=backup_record|BackupType|desktop|EndEpochTime|1169098801|Result|pre-backup:256|StartEpochTime|1169098800
Jan 19 04:02:37 catimor kernel: swap_free: Bad swap offset entry 037ff800

------------------
Server hung
------------------
Jan 18 15:40:01 catimor /etc/e-smith/web/panels/manager/cgi-bin/backup[4773]: /home/e-smith/db/backups: NEW 1169098800=backup_record|BackupType|desktop|EndEpochTime|1169098801|Result|pre-backup:256|StartEpochTime|1169098800
Jan 19 04:02:37 catimor kernel: swap_free: Bad swap offset entry 037ff800
Jan 19 04:02:37 catimor last message repeated 3 times
Jan 19 04:02:58 catimor kernel: Unable to handle kernel paging request at virtual address 6fff6c08
Jan 19 04:02:58 catimor kernel:  printing eip:
Jan 19 04:02:58 catimor kernel: c016702d
Jan 19 04:02:58 catimor kernel: *pde = ffffffff
Jan 19 04:02:58 catimor kernel: Oops: 0000 [#1]
Jan 19 04:02:58 catimor kernel: SMP
Jan 19 04:02:58 catimor kernel: Modules linked in: appletalk(U) e100 ipt_ULOG ipt_REJECT ipt_MASQUERADE ipt_state ip_nat_ftp ip_conntrack_ftp iptable_mangle iptable_nat ip_conntrack iptable_filter ip_tables button battery ac uhci_hcd snd_via82xx snd_ac97_codec snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd_page_alloc snd_mpu401_uart snd_rawmidi snd_seq_device snd soundcore mii bonding(U) floppy st dm_snapshot dm_zero dm_mirror ext3 jbd raid1 dm_mod i2o_block i2o_core aic7xxx sd_mod scsi_mod
Jan 19 04:02:58 catimor kernel: CPU:    0
Jan 19 04:02:58 catimor kernel: EIP:    0060:[__link_path_walk+2118/2997]    Not tainted VLI
Jan 19 04:02:58 catimor kernel: EIP:    0060:[<c016702d>]    Not tainted VLI
Jan 19 04:02:58 catimor kernel: EFLAGS: 00010202   (2.6.9-42.0.3.ELsmp)
Jan 19 04:02:58 catimor kernel: EIP is at __link_path_walk+0x846/0xbb5
Jan 19 04:02:58 catimor kernel: eax: 6fff6be0   ebx: 00000000   ecx: c0334fe0   edx: eeeede7c
Jan 19 04:02:58 catimor kernel: esi: eed7d478   edi: 01c5a71f   ebp: eeeedf50   esp: eeeede5c
Jan 19 04:02:58 catimor kernel: ds: 007b   es: 007b   ss: 0068
Jan 19 04:02:58 catimor kernel: Process ps (pid: 3446, threadinfo=eeeed000 task=f5f13a50)
Jan 19 04:02:58 catimor kernel: Stack: 00c617b8 00000004 f7d3c5c4 00000000 00000101 00000000 f681100f f7e93680
Jan 19 04:02:58 catimor kernel:        eed7fd5c 01c5a71f 00000004 f681100b eeeedf50 eeeedf50 eeeedf50 f6811000
Jan 19 04:02:58 catimor kernel:        00000101 c01673df f7d3c5c4 f7e93f80 097e517c bfe7e8bc 00000003 00000101
Jan 19 04:02:58 catimor kernel: Call Trace:
Jan 19 04:02:58 catimor kernel:  [link_path_walk+67/190] link_path_walk+0x43/0xbe
Jan 19 04:02:58 catimor kernel:  [<c01673df>] link_path_walk+0x43/0xbe
Jan 19 04:02:58 catimor kernel:  [__cond_resched+20/57] __cond_resched+0x14/0x39
Jan 19 04:02:58 catimor kernel:  [<c02d2d76>] __cond_resched+0x14/0x39
Jan 19 04:02:58 catimor kernel:  [direct_strncpy_from_user+62/93] direct_strncpy_from_user+0x3e/0x5d
Jan 19 04:02:58 catimor kernel:  [<c01c3292>] direct_strncpy_from_user+0x3e/0x5d
Jan 19 04:02:59 catimor kernel:  [cp_new_stat64+292/313] cp_new_stat64+0x124/0x139
Jan 19 04:02:59 catimor kernel:  [<c0163126>] cp_new_stat64+0x124/0x139
Jan 19 04:02:59 catimor kernel:  [path_lookup+331/383] path_lookup+0x14b/0x17f
Jan 19 04:02:59 catimor kernel:  [<c0167774>] path_lookup+0x14b/0x17f
Jan 19 04:02:59 catimor kernel:  [open_namei+153/1401] open_namei+0x99/0x579
Jan 19 04:02:59 catimor kernel:  [<c0167e4b>] open_namei+0x99/0x579
Jan 19 04:02:59 catimor kernel:  [filp_open+69/112] filp_open+0x45/0x70
Jan 19 04:02:59 catimor kernel:  [<c015a3de>] filp_open+0x45/0x70
Jan 19 04:02:59 catimor kernel:  [__cond_resched+20/57] __cond_resched+0x14/0x39
Jan 19 04:02:59 catimor kernel:  [<c02d2d76>] __cond_resched+0x14/0x39
Jan 19 04:02:59 catimor kernel:  [direct_strncpy_from_user+62/93] direct_strncpy_from_user+0x3e/0x5d
Jan 19 04:02:59 catimor kernel:  [<c01c3292>] direct_strncpy_from_user+0x3e/0x5d
Jan 19 04:02:59 catimor kernel:  [sys_open+49/125] sys_open+0x31/0x7d
Jan 19 04:02:59 catimor kernel:  [<c015a73a>] sys_open+0x31/0x7d
Jan 19 04:02:59 catimor kernel:  [syscall_call+7/11] syscall_call+0x7/0xb
Jan 19 04:02:59 catimor kernel:  [<c02d47cb>] syscall_call+0x7/0xb
Jan 19 04:02:59 catimor kernel: Code: e8 79 f6 ff ff 8b 44 24 20 8b 70 10 31 c0 85 f6 0f 95 c0 85 44 24 10 0f 84 bd 02 00 00 8b 86 9c 00 00 00 85 c0 0f 84 af 02 00 00 <83> 78 28 00 0f 84 a5 02 00 00 8b 44 24 1c 85 c0 74 04 f0 ff 40
Jan 19 04:02:59 catimor kernel:  <0>Fatal exception: panic in 5 seconds

oliwbol

Howto create full backup on Sme server 7.0
« Reply #10 on: January 19, 2007, 02:18:25 AM »
i think that the nightly cron jobs kicked off, hit a memory error and crashed out.  Not good!  this Could be memory?,or probably disk/swap partition? soi did a test on the swap:

 
the test went ok ? I didn't get any errors on the consol nor the msg log ?

-----------
test
-----------
[root@catimor ~]# grep swap /etc/fstab
/dev/main/swap          swap                    swap    defaults        0 0
[root@catimor ~]# swapoff /dev/main/swap [root@catimor ~]# dd if=/dev/zero of=/dev/main/swap
dd: writing to `/dev/main/swap': No space left on device
2097153+0 records in
2097152+0 records out
[root@catimor ~]#
[root@catimor ~]# mkswap /dev/main/swap
Setting up swapspace version 1, size = 1073737 kB [root@catimor ~]# swapon /dev/main/swap

----------------
Msg log
----------------
Jan 19 10:45:29 catimor kernel: input: AT Translated Set 2 keyboard on isa0060/serio0 Jan 19 10:45:45 catimor hald[4019]: Timed out waiting for hotplug event 485. Rebasing to 484 Jan 19 11:05:27 catimor kernel: Adding 1048568k swap on /dev/main/swap.  Priority:-2 extents:1

oliwbol

HELP! – Anyone out there got any ideas on how to fix this?
« Reply #11 on: January 23, 2007, 12:13:39 AM »
Well unfortunately it happened again, the server hung when it was trying to do a backup.

I really don’t know what I can do… I have tested the swap space and it looks like everything is groovy.  

HELP! – Anyone out there got any ideas on how to fix this?

-----------------
Msg log
-----------------
Jan 22 10:43:40 catimor smbd[18039]: [2007/01/22 10:43:40, 0] smbd/service.c:make_connection_snum(620)
Jan 22 10:43:40 catimor smbd[18039]:   '/home/e-smith/files/users/charlesd/home' does not exist or is not a directory, when connecting to [charlesd]
Jan 22 11:21:51 catimor smbd[18059]: [2007/01/22 11:21:51, 0] smbd/service.c:set_current_service(51)
Jan 22 11:21:51 catimor smbd[18059]:   chdir (/home/e-smith/files/ibays/ceo_off_gd/files) failed
Jan 22 11:21:51 catimor smbd[18059]: [2007/01/22 11:21:51, 0] smbd/service.c:set_current_service(51)

-------------
an 22 11:21:51 catimor smbd[18059]: [2007/01/22 11:21:51, 0] smbd/service.c:set_current_service(51)
Jan 22 11:21:51 catimor smbd[18059]:   chdir (/home/e-smith/files/ibays/per_adm_gd/files) failed
Jan 23 02:00:01 catimor /sbin/e-smith/do_backup[18290]: /home/e-smith/db/backups: OLD 1169481601=(undefined)
Jan 23 02:00:01 catimor /sbin/e-smith/do_backup[18290]: /home/e-smith/db/backups: NEW 1169481601=backup_record
Jan 23 02:00:01 catimor /sbin/e-smith/do_backup[18290]: /home/e-smith/db/backups: OLD 1169481601=backup_record
Jan 23 02:00:01 catimor /sbin/e-smith/do_backup[18290]: /home/e-smith/db/backups: NEW 1169481601=backup_record|StartEpochTime|1169481601
Jan 23 02:00:01 catimor /sbin/e-smith/do_backup[18290]: /home/e-smith/db/backups: OLD 1169481601=backup_record|StartEpochTime|1169481601
Jan 23 02:00:01 catimor /sbin/e-smith/do_backup[18290]: /home/e-smith/db/backups: NEW 1169481601=backup_record|BackupType|tape|StartEpochTime|1169481601
Jan 23 02:00:01 catimor esmith::event[18291]: Processing event: pre-backup tape
Jan 23 02:00:01 catimor esmith::event[18291]: Running event handler: /etc/e-smith/events/pre-backup/S10mysql-delete-dumped-tables
Jan 23 02:00:01 catimor esmith::event[18291]: S10mysql-delete-dumped-tables=action|Event|pre-backup|Action|S10mysql-delete-dumped-tables|Start|1169481601 847323|End|1169481601 851971|Elapsed|0.004648
Jan 23 02:00:01 catimor esmith::event[18291]: Running event handler: /etc/e-smith/events/pre-backup/S20mysql-dump-tables
Jan 23 02:00:02 catimor esmith::event[18291]: S20mysql-dump-tables=action|Event|pre-backup|Action|S20mysql-dump-tables|Start|1169481601 852676|End|1169481602 166224|Elapsed|0.313548
Jan 23 02:00:02 catimor esmith::event[18291]: Running event handler: /etc/e-smith/events/pre-backup/S50rewind-tape
Jan 23 02:00:02 catimor esmith::event[18291]: S50rewind-tape=action|Event|pre-backup|Action|S50rewind-tape|Start|1169481602 166807|End|1169481602 370449|Elapsed|0.203642
Jan 23 02:01:57 catimor kernel: Unable to handle kernel paging request at virtual address 40001170
Jan 23 02:01:57 catimor kernel:  printing eip:
Jan 23 02:01:57 catimor kernel: c0147b11
Jan 23 02:01:57 catimor kernel: *pde = 27631001
Jan 23 02:01:57 catimor kernel: Oops: 0002 [#1]
Jan 23 02:01:57 catimor kernel: SMP
Jan 23 02:01:57 catimor kernel: Modules linked in: appletalk(U) e100 ipt_ULOG ipt_REJECT ipt_MASQUERADE ipt_state ip_nat_ftp ip_conntrack_ftp iptable_mangle iptable_nat ip_conntrack iptable_filter ip_tables button battery ac uhci_hcd snd_via82xx snd_ac97_codec snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd_page_alloc snd_mpu401_uart snd_rawmidi snd_seq_device snd soundcore mii bonding(U) floppy st dm_snapshot dm_zero dm_mirror ext3 jbd raid1 dm_mod i2o_block i2o_core aic7xxx sd_mod scsi_mod
Jan 23 02:01:57 catimor kernel: CPU:    0
Jan 23 02:01:57 catimor kernel: EIP:    0060:[free_block+61/214]    Not tainted VLI
Jan 23 02:01:57 catimor kernel: EIP:    0060:[<c0147b11>]    Not tainted VLI
Jan 23 02:01:57 catimor kernel: EFLAGS: 00010016   (2.6.9-42.0.3.ELsmp)
Jan 23 02:01:57 catimor kernel: EIP is at free_block+0x3d/0xd6
Jan 23 02:01:57 catimor kernel: eax: 4000116c   ebx: c17e50a0   ecx: ef8252f0   edx: 00000001
Jan 23 02:01:57 catimor kernel: esi: c1a3a560   edi: 0000001b   ebp: 00000019   esp: f7c8ee7c
Jan 23 02:01:57 catimor kernel: ds: 007b   es: 007b   ss: 0068
Jan 23 02:01:57 catimor kernel: Process kswapd0 (pid: 44, threadinfo=f7c8e000 task=f7cb5670)
Jan 23 02:01:57 catimor kernel: Stack: c1b52090 c1b44000 c1b52090 f11f82b0 0000001b c0147c18 c1b52080 c1a3a560
Jan 23 02:01:57 catimor kernel:        c1b52080 c1b52090 f11f82b0 00000282 c0147f43 f11f8380 f7c8eee8 0000007a
Jan 23 02:01:57 catimor kernel:        c032de78 c0170afe f11f8380 c0170dfc e76d95a8 e76d95b0 00000000 c017117a
Jan 23 02:01:57 catimor kernel: Call Trace:
Jan 23 02:01:57 catimor kernel:  [cache_flusharray+110/156] cache_flusharray+0x6e/0x9c
Jan 23 02:01:57 catimor kernel:  [<c0147c18>] cache_flusharray+0x6e/0x9c
Jan 23 02:01:57 catimor kernel:  [kmem_cache_free+43/57] kmem_cache_free+0x2b/0x39
Jan 23 02:01:57 catimor kernel:  [<c0147f43>] kmem_cache_free+0x2b/0x39
Jan 23 02:01:57 catimor kernel:  [destroy_inode+61/76] destroy_inode+0x3d/0x4c
Jan 23 02:01:57 catimor kernel:  [<c0170afe>] destroy_inode+0x3d/0x4c
Jan 23 02:01:57 catimor kernel:  [dispose_list+78/109] dispose_list+0x4e/0x6d
Jan 23 02:01:57 catimor kernel:  [<c0170dfc>] dispose_list+0x4e/0x6d
Jan 23 02:01:57 catimor kernel:  [prune_icache+403/492] prune_icache+0x193/0x1ec
Jan 23 02:01:57 catimor kernel:  [<c017117a>] prune_icache+0x193/0x1ec
Jan 23 02:01:57 catimor kernel:  [shrink_icache_memory+20/43] shrink_icache_memory+0x14/0x2b
Jan 23 02:01:57 catimor kernel:  [<c01711e7>] shrink_icache_memory+0x14/0x2b
Jan 23 02:01:57 catimor kernel:  [shrink_slab+248/353] shrink_slab+0xf8/0x161
Jan 23 02:01:57 catimor kernel:  [<c01497f8>] shrink_slab+0xf8/0x161
Jan 23 02:01:57 catimor kernel:  [balance_pgdat+481/782] balance_pgdat+0x1e1/0x30e
Jan 23 02:01:57 catimor kernel:  [<c014aa93>] balance_pgdat+0x1e1/0x30e
Jan 23 02:01:57 catimor kernel:  [schedule+2157/2267] schedule+0x86d/0x8db
Jan 23 02:01:57 catimor kernel:  [<c02d26bd>] schedule+0x86d/0x8db
Jan 23 02:01:57 catimor kernel:  [prepare_to_wait+18/76] prepare_to_wait+0x12/0x4c
Jan 23 02:01:57 catimor kernel:  [<c0120420>] prepare_to_wait+0x12/0x4c
Jan 23 02:01:57 catimor kernel:  [kswapd+202/204] kswapd+0xca/0xcc
Jan 23 02:01:57 catimor kernel:  [<c014ac8a>] kswapd+0xca/0xcc
Jan 23 02:01:57 catimor kernel:  [autoremove_wake_function+0/45] autoremove_wake_function+0x0/0x2d
Jan 23 02:01:57 catimor kernel:  [<c01204f5>] autoremove_wake_function+0x0/0x2d
Jan 23 02:01:57 catimor kernel:  [ret_from_fork+6/20] ret_from_fork+0x6/0x14
Jan 23 02:01:57 catimor kernel:  [<c02d46e6>] ret_from_fork+0x6/0x14
Jan 23 02:01:57 catimor kernel:  [autoremove_wake_function+0/45] autoremove_wake_function+0x0/0x2d
Jan 23 02:01:57 catimor kernel:  [<c01204f5>] autoremove_wake_function+0x0/0x2d
Jan 23 02:01:57 catimor kernel:  [kswapd+0/204] kswapd+0x0/0xcc
Jan 23 02:01:57 catimor kernel:  [<c014abc0>] kswapd+0x0/0xcc
Jan 23 02:01:57 catimor kernel:  [kernel_thread_helper+5/11] kernel_thread_helper+0x5/0xb
Jan 23 02:01:57 catimor kernel:  [<c01041f5>] kernel_thread_helper+0x5/0xb
Jan 23 02:01:57 catimor kernel: Code: 00 00 39 fd 0f 8d b4 00 00 00 8b 04 24 8b 15 90 1a 44 c0 8b 0c a8 8d 81 00 00 00 40 c1 e8 0c c1 e0 05 8b 5c 10 1c 8b 53 04 8b 03 <89> 50 04 89 02 31 d2 2b 4b 0c c7 03 00 01 10 00 c7 43 04 00 02
Jan 23 02:01:57 catimor kernel:  <0>Fatal exception: panic in 5 seconds

Offline pfloor

  • *****
  • 889
  • +1/-0
Howto create full backup on Sme server 7.0
« Reply #12 on: January 23, 2007, 12:22:40 AM »
Jan 22 10:43:40 catimor smbd[18039]: '/home/e-smith/files/users/charlesd/home' does not exist or is not a directory, when connecting to [charlesd]
Jan 22 11:21:51 catimor smbd[18059]: chdir (/home/e-smith/files/ibays/ceo_off_gd/files) failed
Jan 22 11:21:51 catimor smbd[18059]: chdir (/home/e-smith/files/ibays/per_adm_gd/files) failed

Did you remove these directories? if not, possibly you have a drive going bad.

Looks like you may be experiencing some hardware problems.  What are your hardware specs?
In life, you must either "Push, Pull or Get out of the way!"

oliwbol

Howto create full backup on Sme server 7.0
« Reply #13 on: January 23, 2007, 04:25:35 AM »
Hello Paul

Thanks for the response,

Those directories exist, I have not removed them, that part of the log actually names 90% of the file structure in the ibays. Hardware wise It’s a yum cha (generic brand) Pentium III 2 Ghz with 1GB RAM and 2 SCSI 40GB HDDs.

Is there any sort of chkdsk.exe command in SME server like in DOS? How do you go about checking disks and repairing them, or do I have to get rid of the drives?

olie