Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 5 replies
  • Subscribers 4 subscribers
  • Views 2305 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Web Protection Reporting / Rebuild DB not working

Chris -

Web Protection Reporting is empty (double-checked Reporting Settings).

So i tried to rebuild the postgresqldb (found that on other threads), as root:

chown: changing ownership of `/var/storage/pgsql92/data': Read-only file system
Rebuilding PostgreSQL database, all reporting data will be lost!
Enter "yes" to continue...
yes
chown: changing ownership of `/var/storage/pgsql92/data': Read-only file system
:: Stopping PostgreSQLpg_ctl: PID file "/var/storage/pgsql92/data/postmaster.pid" does not exist
Is server running?
failed
rm: cannot remove `/var/storage/pgsql92/data/pg_clog/0060': Read-only file system
rm: cannot remove `/var/storage/pgsql92/data/pg_clog/0019': Read-only file system
[...]
rm: cannot remove `/var/storage/pgsql92/data/pg_clog/0059': Read-only file system
rm: cannot remove `/var/storage/pgsql92/data/pg_hba.conf': Read-only file system
rm: cannot remove `/var/storage/pgsql92/data/pg_ident.conf': Read-only file system
rm: cannot remove `/var/storage/pgsql92/data/pg_multixact/members/0000': Read-only file system
rm: cannot remove `/var/storage/pgsql92/data/pg_multixact/offsets/0000': Read-only file system
rm: cannot remove `/var/storage/pgsql92/data/pg_notify/0000': Read-only file system
rm: cannot remove `/var/storage/pgsql92/data/pg_serial': Read-only file system
rm: cannot remove `/var/storage/pgsql92/data/pg_snapshots': Read-only file system
rm: cannot remove `/var/storage/pgsql92/data/pg_stat_tmp': Read-only file system
rm: cannot remove `/var/storage/pgsql92/data/pg_subtrans/0624': Read-only file system
rm: cannot remove `/var/storage/pgsql92/data/pg_tblspc/16774': Read-only file system
rm: cannot remove `/var/storage/pgsql92/data/pg_twophase': Read-only file system
rm: cannot remove `/var/storage/pgsql92/data/pg_xlog/00000001000000B200000086': Read-only file system
[...]
rm: cannot remove `/var/storage/pgsql92/data/pg_xlog/00000001000000B200000051': Read-only file system
rm: cannot remove `/var/storage/pgsql92/data/pg_xlog/archive_status/00000001000000B20000006A.done': Read-only file system
[...]
rm: cannot remove `/var/storage/pgsql92/data/pg_xlog/archive_status/00000001000000B20000004D.done': Read-only file system
rm: cannot remove `/var/storage/pgsql92/data/pg_xlog/00000001000000B20000004C': Read-only file system
[...]
rm: cannot remove `/var/storage/pgsql92/data/pg_xlog/00000001000000B200000053': Read-only file system
rm: cannot remove `/var/storage/pgsql92/data/postgresql.conf': Read-only file system
rm: cannot remove `/var/storage/pgsql92/data/postmaster.opts': Read-only file system
chown: changing ownership of `/var/storage/pgsql92/data': Read-only file system
:: Initializing the PostgreSQL databaseinitdb: directory "/var/storage/pgsql92/data" exists but is not empty
If you want to create a new database system, either remove or empty
the directory "/var/storage/pgsql92/data" or run initdb
with an argument other than "/var/storage/pgsql92/data".
done
:: Starting PostgreSQLpg_ctl: could not start server
Examine the log output.
failed
:: Restarting SMTP Proxy
:: Stopping SMTP Proxy
cat: /var/chroot-smtp/tmp/ram/pid/master: No such file or directory
cat: /var/chroot-smtp/tmp/ram/pid/sandbox_watcher: No such file or directory
cat: /var/chroot-smtp/tmp/ram/pid/master: No such file or directory
[ ok ]
:: Starting SMTP Proxy
mv: cannot move `/var/chroot-smtp/tmp/smtpd_debug.log' to `/var/chroot-smtp/tmp/smtpd_debug.old.log': Read-only file system
mkdir("/tmp/pdk-MailerDaemon-10826/") failed, errno=30
Can't find temp directory at perlapp line 911.
BEGIN failed--compilation aborted at perlapp line 1003.
BEGIN failed--compilation aborted at -e line 11.
[ ok ]
[ ok ]

What´s going on here? Help! :)

Thanks!



This thread was automatically locked due to age.
Parents
  • 0

    Read-only file system

    Something happened to the storage partition, probably a hard crash.

    The filesystem needs to be repaired (fsck) first.

  • 0 in reply to Alan Brand

    How to do a fsck? Found different Posts on this topic...no real documentation.

    SSH: Tried "system fsck-on-nextboot" --> Command not found.

  • 0 in reply to Chris -
    Chris - said:
    SSH: Tried "system fsck-on-nextboot" --> Command not found.

    This is for sophos XG breed of firewalls, not UTM.

    Manual:

    • Find out the partition mounted to storage (mine is /dev/sda5) by typing "mount":
      /dev/sda5 on /var/storage type ext4 (rw,noatime,discard)
    • umount it: "umount /dev/sda5"
    • check it: "e2fsck /devsda5"
    • reboot.

    I think you can also simply do "touch /forcefsck" and reboot.

    However, if your device is still under maintenance just open a case with sophos, let them dial in and fix it.

  • 0 in reply to Alan Brand

    Thx, will try that!

    No Warranty, just Sophos UTM Home Free :).

  • 0 in reply to Chris -

    What is your backup strategy? If there is significant file system corruption - due to ?? 

    Utm has the smartctl tool.  See what smart values it reads from your storage device

    smartctl -x /dev/sda 

    (or sdb, whatever your hd is identified as).

    I have the system email me weekly config files. Aside from that, the system is imaged quarterly. Over the last few years most of it hasn't changed much.  If I make many setting changes, I'll do a manual backup and send it to myself.

    If it were to crash today, I'd restore july 1st's backup, then last friday configuration.  I'd lose logs between july 1 and today, but that's ok too.  It's a reasonable medium.  I see no point in imaging it more often.

Reply
  • 0 in reply to Chris -

    What is your backup strategy? If there is significant file system corruption - due to ?? 

    Utm has the smartctl tool.  See what smart values it reads from your storage device

    smartctl -x /dev/sda 

    (or sdb, whatever your hd is identified as).

    I have the system email me weekly config files. Aside from that, the system is imaged quarterly. Over the last few years most of it hasn't changed much.  If I make many setting changes, I'll do a manual backup and send it to myself.

    If it were to crash today, I'd restore july 1st's backup, then last friday configuration.  I'd lose logs between july 1 and today, but that's ok too.  It's a reasonable medium.  I see no point in imaging it more often.

Children
No Data
Unfiltered HTML