I updated my FW firmware yesterday to SFOS 16.05.8 MR-8. I became slightly worried after approximately 1 hour and the system had not booted back up so I looked further to find the following. The firmware update had completed After completion all settings had been restored back to factory default - My FW rules had disappeared along with almost everything else The Management IP and default port had restored back to its original setting I could still log into the GUI with my old credentials I created a FW rule to see if I could temporarily pass traffic, this was an ANY/ANY permit rule. This, however, didn't work and when I checked the logs, I saw that traffic was hitting the default rule 0 and being dropped regardless of rules I had in place. After troubleshooting for some time I decided to revert back to the older firmware version and by surprise, everything returned again. Has anybody encountered this? This version doesn't seem stable enough for me to attempt the update again.

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

SFOS 16.05.8 MR-8 Failed Update

I updated my FW firmware yesterday to SFOS 16.05.8 MR-8.

I became slightly worried after approximately 1 hour and the system had not booted back up so I looked further to find the following.

The firmware update had completed

After completion all settings had been restored back to factory default - My FW rules had disappeared along with almost everything else

The Management IP and default port had restored back to its original setting

I could still log into the GUI with my old credentials

I created a FW rule to see if I could temporarily pass traffic, this was an ANY/ANY permit rule. This, however, didn't work and when I checked the logs, I saw that traffic was hitting the default rule 0 and being dropped regardless of rules I had in place.

After troubleshooting for some time I decided to revert back to the older firmware version and by surprise, everything returned again.

Has anybody encountered this? This version doesn't seem stable enough for me to attempt the update again.

This thread was automatically locked due to age.

Parents

0 lferrara over 7 years ago

KelvinCharles,

before moving again to MR8, make sure to create a backup and try again.

You can find additional information from advanced shell

cd /log and then

cat migration.log

Regards
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 lferrara over 7 years ago

KelvinCharles,

before moving again to MR8, make sure to create a backup and try again.

You can find additional information from advanced shell

cd /log and then

cat migration.log

Regards
Cancel
Vote Up 0 Vote Down

Cancel

Children

0 Feuxlin over 7 years ago in reply to lferrara

KevinCharles,

I was having the same issue, when upgrading to MR8 the Firewall went to some hybridization of the default config (My users and passwords worked, but all of my rules/interfaces/etc were lost. Thinking I had mistakenly clicked on the "Boot to Image with Factory Firmware" I reverted back to the old firmware (MR7) and all of my configs were restored. On a lark I downloaded XG17 to see if a milestone update might succeed where the maintenance release failed, but it did not. It also reverts my config back. I restored a backup I had and the firewall is working as intended on version 17, but I need to know what happened so I don't revert a remote box that I don't have immediate access to. below is the migration.log from the device.

Any direction or advice would be appreciated, I will likely be opening a ticket with support later today in any case.

Just so that it is apparent, this Firewall was "Prestaged" for a client and boxed up, we got it out today to do final prep and updates, that is why there is a gap in the log.

Sophos Firmware Version SFOS 17.0.0 GA

Main Menu

1. Network Configuration
2. System Configuration
3. Route Configuration
4. Device Console
5. Device Management
6. VPN Management
7. Shutdown/Reboot Device
0. Exit

Select Menu Number [0-7]: 5

Sophos Firmware Version SFOS 17.0.0 GA

Device Management

1. Reset to Factory Defaults
2. Show Firmware(s)
3. Advanced Shell
4. Flush Device Reports
0. Exit

Select Menu Number [0-4]: 3

Sophos Firewall
===============
(C) Copyright 2000-2017 Sophos Limited and others. All rights reserved.
Sophos is a registered trademark of Sophos Limited and Sophos Group.
All other product and company names mentioned are trademarks or registered
trademarks of their respective owners.

For End User License Agreement - www.sophos.com/.../sophos-end-us er-license-agreement.aspx

NOTE: If not explicitly approved by Sophos support, any modifications
done through this option will void your support.

XG125_XN02_SFOS 17.0.0 GA# cd /log
XG125_XN02_SFOS 17.0.0 GA# cat migration.log
Wed Aug 30 18:40:54 UTC 2017 starting old version corporate db
Starting conf database
231 2017-08-30 18:40:55.218 GMTLOG: could not connect socket for statistics col lector: Network is unreachable
231 2017-08-30 18:40:55.218 GMTLOG: disabling statistics collector for lack of working socket
233 2017-08-30 18:40:55.220 GMTLOG: database system was shut down at 2017-08-30 18:40:19 GMT
init_g_svc: shm_open(/svc0x0001) failed: No such file or directory
231 2017-08-30 18:40:55.235 GMTLOG: database system is ready to accept connecti ons
database started
svc_set_status: svc_init not done
DELETE 0
DELETE 0
DELETE 0
DELETE 0
Stopping database
231 2017-08-30 18:41:07.740 GMTLOG: received fast shutdown request
231 2017-08-30 18:41:07.740 GMTLOG: aborting any active transactions
234 2017-08-30 18:41:07.740 GMTLOG: shutting down
234 2017-08-30 18:41:07.787 GMTLOG: database system is shut down
/sdisk/oldpgconfdump.sql is created
Starting conf database
272 2017-08-30 18:41:17.762 GMTLOG: could not connect socket for statistics col lector: Network is unreachable
272 2017-08-30 18:41:17.762 GMTLOG: disabling statistics collector for lack of working socket
274 2017-08-30 18:41:17.764 GMTLOG: database system was shut down at 2017-08-20 00:03:19 GMT
init_g_svc: shm_open(/svc0x0001) failed: No such file or directory
272 2017-08-30 18:41:17.770 GMTLOG: database system is ready to accept connecti ons
database started
svc_set_status: svc_init not done
DROP SCHEMA config CASCADE
DROP SCHEMA
DROP SCHEMA public CASCADE
DROP SCHEMA
DROP PROCEDURAL LANGUAGE plpgsql
283 2017-08-30 18:41:28.393 GMTERROR: cannot drop language plpgsql because exte nsion plpgsql requires it
283 2017-08-30 18:41:28.393 GMTHINT: You can drop extension plpgsql instead.
283 2017-08-30 18:41:28.393 GMTSTATEMENT: DROP PROCEDURAL LANGUAGE plpgsql
ERROR: cannot drop language plpgsql because extension plpgsql requires it
HINT: You can drop extension plpgsql instead.
CREATE SCHEMA public
CREATE SCHEMA
275 2017-08-30 18:41:29.680 GMTLOG: checkpoints are occurring too frequently (1 2 seconds apart)
275 2017-08-30 18:41:29.680 GMTHINT: Consider increasing the configuration para meter "checkpoint_segments".
psql:/sdisk/oldpgconfdump.sql:14766: WARNING: column "senderemail" has type "un known"
DETAIL: Proceeding with relation creation anyway.
psql:/sdisk/oldpgconfdump.sql:14766: WARNING: column "receipientemail" has type "unknown"
DETAIL: Proceeding with relation creation anyway.
setval
--------
160
(1 row)

setval
--------
1
(1 row)

setval
--------
1
(1 row)

setval
--------
1
(1 row)

setval
--------
1
(1 row)

setval
--------
64
(1 row)

275 2017-08-30 18:41:33.114 GMTLOG: checkpoints are occurring too frequently (4 seconds apart)
275 2017-08-30 18:41:33.114 GMTHINT: Consider increasing the configuration para meter "checkpoint_segments".
Stopping database
272 2017-08-30 18:41:40.000 GMTLOG: received fast shutdown request
272 2017-08-30 18:41:40.000 GMTLOG: aborting any active transactions
275 2017-08-30 18:41:40.089 GMTLOG: shutting down
275 2017-08-30 18:41:40.236 GMTLOG: database system is shut down
old conf to new conf migrated with return value :: 0
Wed Aug 30 19:41:48 BST 2017 starting migration log
Starting conf database
311 2017-08-30 18:41:48.254 GMTLOG: could not connect socket for statistics col lector: Network is unreachable
311 2017-08-30 18:41:48.255 GMTLOG: disabling statistics collector for lack of working socket
313 2017-08-30 18:41:48.257 GMTLOG: database system was shut down at 2017-08-30 18:41:40 GMT
init_g_svc: shm_open(/svc0x0001) failed: No such file or directory
311 2017-08-30 18:41:48.263 GMTLOG: database system is ready to accept connecti ons
database started
svc_set_status: svc_init not done
UPDATE 1
INSERT 0 0
INSERT 0 0
INSERT 0 0
INSERT 0 0
INSERT 0 0
INSERT 0 0
INSERT 0 0
INSERT 0 0
INSERT 0 0
INSERT 0 0
INSERT 0 0
INSERT 0 1
Old version is 16.508 and currentversion is 16.510
Database is upgrading to dbv16.509
Check migration for version dbv16.509
Applying migration for version dbv16.509
Database is upgrading to dbv16.510
Check migration for version dbv16.510
Applying migration for version dbv16.510
create_pguser
---------------

(1 row)

UPDATE 1
Stopping database
311 2017-08-30 18:42:01.069 GMTLOG: received fast shutdown request
311 2017-08-30 18:42:01.069 GMTLOG: aborting any active transactions
314 2017-08-30 18:42:01.070 GMTLOG: shutting down
314 2017-08-30 18:42:01.166 GMTLOG: database system is shut down
applymigration.sh exited with 0
Doing /conf/certificate/cacerts/
WARNING: Skipping expired Certificate TURKTRUST_Certificate_Services_Provider_Ro ot_2.pem
WARNING: Skipping expired Certificate E_Guven_Kok_Elektronik_Sertifika_Hizmet_Sa glayicisi.pem
WARNING: Skipping expired Certificate CA_Disig.pem
WARNING: Skipping expired Certificate STATIC_MSIT_Machine_Auth_CA_2.pem
WARNING: Skipping expired Certificate TÜBİTAK_UEKAE_Kök_Sertifika_Hizmet_Sağlayı cısı_Sürüm_3.pem
WARNING: Skipping expired Certificate EBG_Elektronik_Sertifika_Hizmet_Sağlayıcıs ı.pem
WARNING: Skipping duplicate certificate RSA_Root_Certificate_1.pem
WARNING: Skipping expired Certificate A_Trust_nQual_03.pem
WARNING: Skipping duplicate certificate AAACertificateServices.pem
WARNING: Skipping expired Certificate TURKTRUSTElektronikSertifikaHizmetSaglayic isi_2.pem
WARNING: Skipping expired Certificate Microsec_e_Szigno_Root_CA.pem
WARNING: Skipping expired Certificate Buypass_Class_2_CA_1.pem
WARNING: Skipping duplicate certificate GlobalSignRootCA_3.pem
WARNING: Skipping duplicate certificate Comodo_Secure_Services_root.pem
WARNING: Skipping expired Certificate Staat_der_Nederlanden_Root_CA.pem
WARNING: Skipping expired Certificate Juur_SK.pem
WARNING: Skipping expired Certificate STATIC_VeriSign_Inc_VeriSign_Class_3_Exten ded_Validation_SSL_SGC_CA.pem
WARNING: Skipping duplicate certificate Certum_Root_CA.pem
Fri Oct 27 15:29:55 UTC 2017 starting old version corporate db
Starting conf database
235 2017-10-27 15:29:56.468 GMTLOG: could not connect socket for statistics col lector: Network is unreachable
235 2017-10-27 15:29:56.469 GMTLOG: disabling statistics collector for lack of working socket
237 2017-10-27 15:29:56.471 GMTLOG: database system was shut down at 2017-10-27 15:29:19 GMT
init_g_svc: shm_open(/svc0x0001) failed: No such file or directory
235 2017-10-27 15:29:56.484 GMTLOG: database system is ready to accept connecti ons
database started
svc_set_status: svc_init not done
DELETE 0
DELETE 0
DELETE 0
DELETE 0
Stopping database
235 2017-10-27 15:30:13.504 GMTLOG: received fast shutdown request
235 2017-10-27 15:30:13.504 GMTLOG: aborting any active transactions
238 2017-10-27 15:30:13.504 GMTLOG: shutting down
238 2017-10-27 15:30:13.563 GMTLOG: database system is shut down
/sdisk/oldpgconfdump.sql is created
Starting conf database
276 2017-10-27 15:30:23.487 GMTLOG: could not connect socket for statistics col lector: Network is unreachable
276 2017-10-27 15:30:23.487 GMTLOG: disabling statistics collector for lack of working socket
278 2017-10-27 15:30:23.489 GMTLOG: database system was shut down at 2017-09-27 08:55:08 GMT
init_g_svc: shm_open(/svc0x0001) failed: No such file or directory
276 2017-10-27 15:30:23.500 GMTLOG: database system is ready to accept connecti ons
database started
svc_set_status: svc_init not done
DROP SCHEMA config CASCADE
DROP SCHEMA
DROP SCHEMA public CASCADE
DROP SCHEMA
DROP PROCEDURAL LANGUAGE plpgsql
287 2017-10-27 15:30:34.143 GMTERROR: cannot drop language plpgsql because exte nsion plpgsql requires it
287 2017-10-27 15:30:34.143 GMTHINT: You can drop extension plpgsql instead.
287 2017-10-27 15:30:34.143 GMTSTATEMENT: DROP PROCEDURAL LANGUAGE plpgsql
ERROR: cannot drop language plpgsql because extension plpgsql requires it
HINT: You can drop extension plpgsql instead.
CREATE SCHEMA public
CREATE SCHEMA
279 2017-10-27 15:30:35.323 GMTLOG: checkpoints are occurring too frequently (1 2 seconds apart)
279 2017-10-27 15:30:35.323 GMTHINT: Consider increasing the configuration para meter "checkpoint_segments".
279 2017-10-27 15:30:40.186 GMTLOG: checkpoints are occurring too frequently (5 seconds apart)
279 2017-10-27 15:30:40.186 GMTHINT: Consider increasing the configuration para meter "checkpoint_segments".
psql:/sdisk/oldpgconfdump.sql:27295: WARNING: column "senderemail" has type "un known"
DETAIL: Proceeding with relation creation anyway.
psql:/sdisk/oldpgconfdump.sql:27295: WARNING: column "receipientemail" has type "unknown"
DETAIL: Proceeding with relation creation anyway.
psql:/sdisk/oldpgconfdump.sql:29720: WARNING: column "senderemail" has type "un known"
DETAIL: Proceeding with relation creation anyway.
psql:/sdisk/oldpgconfdump.sql:29720: WARNING: column "receipientemail" has type "unknown"
DETAIL: Proceeding with relation creation anyway.
setval
--------
160
(1 row)

setval
--------
1
(1 row)

setval
--------
1
(1 row)

setval
--------
1
(1 row)

setval
--------
1
(1 row)

setval
--------
64
(1 row)

setval
--------
160
(1 row)

setval
--------
1
(1 row)

setval
--------
1
(1 row)

setval
--------
1
(1 row)

setval
--------
1
(1 row)

setval
--------
64
(1 row)

279 2017-10-27 15:30:43.133 GMTLOG: checkpoints are occurring too frequently (3 seconds apart)
279 2017-10-27 15:30:43.133 GMTHINT: Consider increasing the configuration para meter "checkpoint_segments".
279 2017-10-27 15:30:53.965 GMTLOG: checkpoints are occurring too frequently (1 0 seconds apart)
279 2017-10-27 15:30:53.965 GMTHINT: Consider increasing the configuration para meter "checkpoint_segments".
Stopping database
276 2017-10-27 15:30:56.981 GMTLOG: received fast shutdown request
276 2017-10-27 15:30:56.981 GMTLOG: aborting any active transactions
279 2017-10-27 15:30:57.090 GMTLOG: shutting down
279 2017-10-27 15:30:57.202 GMTLOG: database system is shut down
old conf to new conf migrated with return value :: 0
Fri Oct 27 11:31:05 EDT 2017 starting migration log
Starting conf database
315 2017-10-27 15:31:05.239 GMTLOG: could not connect socket for statistics col lector: Network is unreachable
315 2017-10-27 15:31:05.239 GMTLOG: disabling statistics collector for lack of working socket
317 2017-10-27 15:31:05.241 GMTLOG: database system was shut down at 2017-10-27 15:30:57 GMT
init_g_svc: shm_open(/svc0x0001) failed: No such file or directory
315 2017-10-27 15:31:05.248 GMTLOG: database system is ready to accept connecti ons
database started
svc_set_status: svc_init not done
UPDATE 1
INSERT 0 0
INSERT 0 0
INSERT 0 0
INSERT 0 0
INSERT 0 0
INSERT 0 0
INSERT 0 0
INSERT 0 0
INSERT 0 0
INSERT 0 0
INSERT 0 0
INSERT 0 1
Old version is 16.510 and currentversion is 16.511
Database is upgrading to dbv16.511
Check migration for version dbv16.511
Applying migration for version dbv16.511
1086 2017-10-27 15:31:15.722 GMTERROR: cannot drop function fn_reference_iface( ) because other objects depend on it
1086 2017-10-27 15:31:15.722 GMTDETAIL: trigger tg_reference_iface on table exp ortconfig.tblmcastroutingdetail depends on function fn_reference_iface()
1086 2017-10-27 15:31:15.722 GMTHINT: Use DROP ... CASCADE to drop the dependen t objects too.
1086 2017-10-27 15:31:15.722 GMTSTATEMENT: DROP FUNCTION IF EXISTS fn_reference _iface();
psql:/_conf/DB/validationTrigger.sql:2128: ERROR: cannot drop function fn_refer ence_iface() because other objects depend on it
DETAIL: trigger tg_reference_iface on table exportconfig.tblmcastroutingdetail depends on function fn_reference_iface()
HINT: Use DROP ... CASCADE to drop the dependent objects too.
validation trigger file : /_conf//DB/validationTrigger.sql failed
UPDATE 1
Stopping database
315 2017-10-27 15:31:17.603 GMTLOG: received fast shutdown request
315 2017-10-27 15:31:17.603 GMTLOG: aborting any active transactions
318 2017-10-27 15:31:17.604 GMTLOG: shutting down
318 2017-10-27 15:31:17.668 GMTLOG: database system is shut down
applymigration.sh exited with 1
Fri Oct 27 15:51:07 UTC 2017 starting old version corporate db
Starting conf database
236 2017-10-27 15:51:08.616 GMTLOG: could not connect socket for statistics col lector: Network is unreachable
236 2017-10-27 15:51:08.616 GMTLOG: disabling statistics collector for lack of working socket
238 2017-10-27 15:51:08.619 GMTLOG: database system was shut down at 2017-10-27 15:50:32 GMT
init_g_svc: shm_open(/svc0x0001) failed: No such file or directory
236 2017-10-27 15:51:08.634 GMTLOG: database system is ready to accept connecti ons
database started
svc_set_status: svc_init not done
DELETE 0
DELETE 0
DELETE 0
DELETE 0
Stopping database
236 2017-10-27 15:51:25.668 GMTLOG: received fast shutdown request
236 2017-10-27 15:51:25.668 GMTLOG: aborting any active transactions
239 2017-10-27 15:51:25.669 GMTLOG: shutting down
239 2017-10-27 15:51:25.720 GMTLOG: database system is shut down
/sdisk/oldpgconfdump.sql is created
Starting conf database
277 2017-10-27 15:51:35.600 GMTLOG: could not connect socket for statistics col lector: Network is unreachable
277 2017-10-27 15:51:35.600 GMTLOG: disabling statistics collector for lack of working socket
279 2017-10-27 15:51:35.602 GMTLOG: database system was shut down at 2017-09-27 08:55:08 GMT
init_g_svc: shm_open(/svc0x0001) failed: No such file or directory
277 2017-10-27 15:51:35.607 GMTLOG: database system is ready to accept connecti ons
database started
svc_set_status: svc_init not done
DROP SCHEMA config CASCADE
DROP SCHEMA
DROP SCHEMA public CASCADE
DROP SCHEMA
DROP PROCEDURAL LANGUAGE plpgsql
288 2017-10-27 15:51:46.268 GMTERROR: cannot drop language plpgsql because exte nsion plpgsql requires it
288 2017-10-27 15:51:46.268 GMTHINT: You can drop extension plpgsql instead.
288 2017-10-27 15:51:46.268 GMTSTATEMENT: DROP PROCEDURAL LANGUAGE plpgsql
ERROR: cannot drop language plpgsql because extension plpgsql requires it
HINT: You can drop extension plpgsql instead.
CREATE SCHEMA public
CREATE SCHEMA
280 2017-10-27 15:51:47.454 GMTLOG: checkpoints are occurring too frequently (1 2 seconds apart)
280 2017-10-27 15:51:47.454 GMTHINT: Consider increasing the configuration para meter "checkpoint_segments".
280 2017-10-27 15:51:52.299 GMTLOG: checkpoints are occurring too frequently (5 seconds apart)
280 2017-10-27 15:51:52.299 GMTHINT: Consider increasing the configuration para meter "checkpoint_segments".
psql:/sdisk/oldpgconfdump.sql:27295: WARNING: column "senderemail" has type "un known"
DETAIL: Proceeding with relation creation anyway.
psql:/sdisk/oldpgconfdump.sql:27295: WARNING: column "receipientemail" has type "unknown"
DETAIL: Proceeding with relation creation anyway.
psql:/sdisk/oldpgconfdump.sql:29720: WARNING: column "senderemail" has type "un known"
DETAIL: Proceeding with relation creation anyway.
psql:/sdisk/oldpgconfdump.sql:29720: WARNING: column "receipientemail" has type "unknown"
DETAIL: Proceeding with relation creation anyway.
setval
--------
160
(1 row)

setval
--------
1
(1 row)

setval
--------
1
(1 row)

setval
--------
1
(1 row)

setval
--------
1
(1 row)

setval
--------
64
(1 row)

setval
--------
160
(1 row)

setval
--------
1
(1 row)

setval
--------
1
(1 row)

setval
--------
1
(1 row)

setval
--------
1
(1 row)

setval
--------
64
(1 row)

280 2017-10-27 15:51:55.240 GMTLOG: checkpoints are occurring too frequently (3 seconds apart)
280 2017-10-27 15:51:55.240 GMTHINT: Consider increasing the configuration para meter "checkpoint_segments".
280 2017-10-27 15:52:06.166 GMTLOG: checkpoints are occurring too frequently (1 1 seconds apart)
280 2017-10-27 15:52:06.166 GMTHINT: Consider increasing the configuration para meter "checkpoint_segments".
Stopping database
277 2017-10-27 15:52:09.209 GMTLOG: received fast shutdown request
277 2017-10-27 15:52:09.209 GMTLOG: aborting any active transactions
280 2017-10-27 15:52:09.323 GMTLOG: shutting down
280 2017-10-27 15:52:09.436 GMTLOG: database system is shut down
old conf to new conf migrated with return value :: 0
Fri Oct 27 11:52:17 EDT 2017 starting migration log
Starting conf database
316 2017-10-27 15:52:17.472 GMTLOG: could not connect socket for statistics col lector: Network is unreachable
316 2017-10-27 15:52:17.472 GMTLOG: disabling statistics collector for lack of working socket
318 2017-10-27 15:52:17.475 GMTLOG: database system was shut down at 2017-10-27 15:52:09 GMT
init_g_svc: shm_open(/svc0x0001) failed: No such file or directory
316 2017-10-27 15:52:17.482 GMTLOG: database system is ready to accept connecti ons
database started
svc_set_status: svc_init not done
UPDATE 1
INSERT 0 0
INSERT 0 0
INSERT 0 0
INSERT 0 0
INSERT 0 0
INSERT 0 0
INSERT 0 0
INSERT 0 0
INSERT 0 0
INSERT 0 0
INSERT 0 0
INSERT 0 1
Old version is 16.510 and currentversion is 16.511
Database is upgrading to dbv16.511
Check migration for version dbv16.511
Applying migration for version dbv16.511
1087 2017-10-27 15:52:27.969 GMTERROR: cannot drop function fn_reference_iface( ) because other objects depend on it
1087 2017-10-27 15:52:27.969 GMTDETAIL: trigger tg_reference_iface on table exp ortconfig.tblmcastroutingdetail depends on function fn_reference_iface()
1087 2017-10-27 15:52:27.969 GMTHINT: Use DROP ... CASCADE to drop the dependen t objects too.
1087 2017-10-27 15:52:27.969 GMTSTATEMENT: DROP FUNCTION IF EXISTS fn_reference _iface();
psql:/_conf/DB/validationTrigger.sql:2128: ERROR: cannot drop function fn_refer ence_iface() because other objects depend on it
DETAIL: trigger tg_reference_iface on table exportconfig.tblmcastroutingdetail depends on function fn_reference_iface()
HINT: Use DROP ... CASCADE to drop the dependent objects too.
validation trigger file : /_conf//DB/validationTrigger.sql failed
UPDATE 1
Stopping database
316 2017-10-27 15:52:29.858 GMTLOG: received fast shutdown request
316 2017-10-27 15:52:29.858 GMTLOG: aborting any active transactions
319 2017-10-27 15:52:29.859 GMTLOG: shutting down
319 2017-10-27 15:52:29.924 GMTLOG: database system is shut down
applymigration.sh exited with 1
Fri Oct 27 16:24:55 UTC 2017 starting old version corporate db
Starting conf database
223 2017-10-27 16:24:55.857 GMTLOG: could not connect socket for statistics col lector: Network is unreachable
223 2017-10-27 16:24:55.857 GMTLOG: disabling statistics collector for lack of working socket
225 2017-10-27 16:24:55.860 GMTLOG: database system was shut down at 2017-10-27 16:24:19 GMT
init_g_svc: shm_open(/svc0x0001) failed: No such file or directory
223 2017-10-27 16:24:55.874 GMTLOG: database system is ready to accept connecti ons
database started
svc_set_status: svc_init not done
DELETE 0
DELETE 0
DELETE 0
DELETE 0
Stopping database
223 2017-10-27 16:25:12.911 GMTLOG: received fast shutdown request
223 2017-10-27 16:25:12.911 GMTLOG: aborting any active transactions
226 2017-10-27 16:25:12.911 GMTLOG: shutting down
226 2017-10-27 16:25:12.964 GMTLOG: database system is shut down
/sdisk/oldpgconfdump.sql is created
Starting conf database
265 2017-10-27 16:25:23.109 GMTLOG: could not connect socket for statistics col lector: Network is unreachable
265 2017-10-27 16:25:23.109 GMTLOG: disabling statistics collector for lack of working socket
267 2017-10-27 16:25:23.112 GMTLOG: database system was shut down at 2017-10-20 14:38:02 GMT
init_g_svc: shm_open(/svc0x0001) failed: No such file or directory
265 2017-10-27 16:25:23.121 GMTLOG: database system is ready to accept connecti ons
database started
svc_set_status: svc_init not done
DROP SCHEMA config CASCADE
DROP SCHEMA
DROP SCHEMA public CASCADE
DROP SCHEMA
DROP PROCEDURAL LANGUAGE plpgsql
276 2017-10-27 16:25:33.878 GMTERROR: cannot drop language plpgsql because exte nsion plpgsql requires it
276 2017-10-27 16:25:33.878 GMTHINT: You can drop extension plpgsql instead.
276 2017-10-27 16:25:33.878 GMTSTATEMENT: DROP PROCEDURAL LANGUAGE plpgsql
ERROR: cannot drop language plpgsql because extension plpgsql requires it
HINT: You can drop extension plpgsql instead.
CREATE SCHEMA public
CREATE SCHEMA
268 2017-10-27 16:25:35.000 GMTLOG: checkpoints are occurring too frequently (1 2 seconds apart)
268 2017-10-27 16:25:35.000 GMTHINT: Consider increasing the configuration para meter "checkpoint_segments".
268 2017-10-27 16:25:39.501 GMTLOG: checkpoints are occurring too frequently (4 seconds apart)
268 2017-10-27 16:25:39.501 GMTHINT: Consider increasing the configuration para meter "checkpoint_segments".
psql:/sdisk/oldpgconfdump.sql:27295: WARNING: column "senderemail" has type "un known"
DETAIL: Proceeding with relation creation anyway.
psql:/sdisk/oldpgconfdump.sql:27295: WARNING: column "receipientemail" has type "unknown"
DETAIL: Proceeding with relation creation anyway.
psql:/sdisk/oldpgconfdump.sql:29720: WARNING: column "senderemail" has type "un known"
DETAIL: Proceeding with relation creation anyway.
psql:/sdisk/oldpgconfdump.sql:29720: WARNING: column "receipientemail" has type "unknown"
DETAIL: Proceeding with relation creation anyway.
setval
--------
160
(1 row)

setval
--------
1
(1 row)

setval
--------
1
(1 row)

setval
--------
1
(1 row)

setval
--------
1
(1 row)

setval
--------
64
(1 row)

setval
--------
160
(1 row)

setval
--------
1
(1 row)

setval
--------
1
(1 row)

setval
--------
1
(1 row)

setval
--------
1
(1 row)

setval
--------
64
(1 row)

268 2017-10-27 16:25:42.683 GMTLOG: checkpoints are occurring too frequently (3 seconds apart)
268 2017-10-27 16:25:42.683 GMTHINT: Consider increasing the configuration para meter "checkpoint_segments".
268 2017-10-27 16:25:53.180 GMTLOG: checkpoints are occurring too frequently (1 1 seconds apart)
268 2017-10-27 16:25:53.180 GMTHINT: Consider increasing the configuration para meter "checkpoint_segments".
Stopping database
265 2017-10-27 16:25:57.010 GMTLOG: received fast shutdown request
265 2017-10-27 16:25:57.010 GMTLOG: aborting any active transactions
268 2017-10-27 16:25:57.166 GMTLOG: shutting down
268 2017-10-27 16:25:57.260 GMTLOG: database system is shut down
old conf to new conf migrated with return value :: 0
Fri Oct 27 12:26:05 EDT 2017 starting migration log
Starting conf database
304 2017-10-27 16:26:05.283 GMTLOG: could not connect socket for statistics col lector: Network is unreachable
304 2017-10-27 16:26:05.283 GMTLOG: disabling statistics collector for lack of working socket
306 2017-10-27 16:26:05.286 GMTLOG: database system was shut down at 2017-10-27 16:25:57 GMT
init_g_svc: shm_open(/svc0x0001) failed: No such file or directory
304 2017-10-27 16:26:05.292 GMTLOG: database system is ready to accept connecti ons
database started
svc_set_status: svc_init not done
UPDATE 1
INSERT 0 0
INSERT 0 0
INSERT 0 0
INSERT 0 0
INSERT 0 0
INSERT 0 0
INSERT 0 0
INSERT 0 0
INSERT 0 0
INSERT 0 0
INSERT 0 0
INSERT 0 1
Old version is 16.510 and currentversion is 17.105
Database is upgrading to dbv16.511
Check migration for version dbv16.511
Applying migration for version dbv16.511
Database is upgrading to dbv17.100
Check migration for version dbv17.100
Applying migration for version dbv17.100
add_load_balance_if_no_records
--------------------------------

(1 row)

update_custom_category_messages
---------------------------------

(1 row)

no files found matching '/conf/ipsec/strongswan.d/charon/ha.conf'
Database is upgrading to dbv17.101
Check migration for version dbv17.101
Applying migration for version dbv17.101
Database is upgrading to dbv17.102
Check migration for version dbv17.102
Applying migration for version dbv17.102
adddbv16511
-------------

(1 row)

Database is upgrading to dbv17.103
Check migration for version dbv17.103
Applying migration for version dbv17.103
add_policy_tester_scheme
--------------------------

(1 row)

add_policy_tester_scheme
--------------------------

(1 row)

add_policy_tester_scheme
--------------------------

(1 row)

add_policy_tester_scheme
--------------------------

(1 row)

add_policy_tester_scheme
--------------------------

(1 row)

add_policy_tester_scheme
--------------------------

(1 row)

add_policy_tester_scheme
--------------------------

(1 row)

add_policy_tester_scheme
--------------------------

(1 row)

add_policy_tester_scheme
--------------------------

(1 row)

add_policy_tester_scheme
--------------------------

(1 row)

add_policy_tester_scheme
--------------------------

(1 row)

add_policy_tester_scheme
--------------------------

(1 row)

add_policy_tester_scheme
--------------------------

(1 row)

add_policy_tester_scheme
--------------------------

(1 row)

add_policy_tester_scheme
--------------------------

(1 row)

add_policy_tester_scheme
--------------------------

(1 row)

add_policy_tester_scheme
--------------------------

(1 row)

add_policy_tester_scheme
--------------------------

(1 row)

add_policy_tester_scheme
--------------------------

(1 row)

add_policy_tester_scheme
--------------------------

(1 row)

Database is upgrading to dbv17.104
Check migration for version dbv17.104
Applying migration for version dbv17.104
convert_tbleacapplications_qualify_type
-----------------------------------------

(1 row)

Database is upgrading to dbv17.105
Check migration for version dbv17.105
Applying migration for version dbv17.105
DELETE 0
DELETE 1
DELETE 1
1154 2017-10-27 16:26:19.077 GMTERROR: cannot drop function fn_reference_iface( ) because other objects depend on it
1154 2017-10-27 16:26:19.077 GMTDETAIL: trigger tg_reference_iface on table exp ortconfig.tblmcastroutingdetail depends on function fn_reference_iface()
1154 2017-10-27 16:26:19.077 GMTHINT: Use DROP ... CASCADE to drop the dependen t objects too.
1154 2017-10-27 16:26:19.077 GMTSTATEMENT: DROP FUNCTION IF EXISTS fn_reference _iface();
psql:/_conf/DB/validationTrigger.sql:2227: ERROR: cannot drop function fn_refer ence_iface() because other objects depend on it
DETAIL: trigger tg_reference_iface on table exportconfig.tblmcastroutingdetail depends on function fn_reference_iface()
HINT: Use DROP ... CASCADE to drop the dependent objects too.
validation trigger file : /_conf//DB/validationTrigger.sql failed
UPDATE 1
Stopping database
304 2017-10-27 16:26:21.085 GMTLOG: received fast shutdown request
304 2017-10-27 16:26:21.085 GMTLOG: aborting any active transactions
307 2017-10-27 16:26:21.086 GMTLOG: shutting down
307 2017-10-27 16:26:21.287 GMTLOG: database system is shut down
applymigration.sh exited with 1
XG125_XN02_SFOS 17.0.0 GA#
Cancel
Vote Up 0 Vote Down

Cancel