Usul 5.3.8-1 over Usul 5.3.7-1 just hosed my system drive...

motox22a · 11. März 2020

System had been working great since upgrade about 2 months ago...

Did the upgrade through OMVExtras GUI...First thing it said was COLORAMA was being removed.
Then I had a banner at the top sayng to APPLY changes (I Did)...
That left me with a dead GUI...Tried SSHing into it to issue reboot but would not do anything...
Power button off...Then back on...Heard the beep and then tried to login...And got NGINX BAD GATEWAY...

First problem I've had with OMV 5... Luckily I image with CLONEZILLA so 5.3.7-1 is being restored now...

System is x86..

Just thought I'd give a heads up on this...

motox22a · 11. März 2020

Back up and running 5.3.7-1...CLONEZILLA saves my @$$ again...

gderf · 11. März 2020

I didn't see anything out of the ordinary. Upgrade went fine.

motox22a · 11. März 2020

I must be a glutton for punishment...
Ran it again over a perfectly good Usul 5.3.7-1 system...
and it again broke the system. Unresponsive...
System is a Dell Optiplex 320 with 4Gb of ram (3.14gb available)
with a Core2 x6800 @2.93Ghz. See attachments...
Ran OMV 4.x and OMV 5.x up to this just fine...

That's enough torture for tonight...Now off to restore (again)...

Frepke · 11. März 2020

Zitat von gderf

I didn't see anything out of the ordinary. Upgrade went fine.

Yeah, upgrade went fine.

votdev · 11. März 2020

You should log into the box via SSH or TTY and run one of the following commands:

omv-salt deploy run nginx (this module was marked dirty during the upgrade) or deploy the whole system with omv-salt stage run deploy.

motox22a · 11. März 2020

votdev,

A REALLY BIG THANK YOU...

After I saw the second guy say his worked...I started investigating...
Ran across a couple of other times this happened...It's most surely tied to the OMV 4 to OMV 5 upgrade...

502 Bad Gateway nginx

I had been trying all those commands but was still not working...I had also tried omv-firstaid for both the NIC and Http port number...
Still was not working...

THANKS for those two commands...
I ran them both via SSH and rebooted... And I am back UP and running on
Usul 5.3.8-1

Mobilis · 11. März 2020

I am having the same issue on two separate machines. I tried the two commands above and I still get the 502 Bad Gateway nginx page.

The first command appears to have succedded however, the second command had the following output.

Bash

root@omv-data:~# omv-salt stage run deploy
/usr/lib/python3/dist-packages/salt/modules/file.py:32: DeprecationWarning: Using or importing the ABCs from 'collections' instead of from 'collections.abc' is deprecated, and in 3.8 it will stop working
  from collections import Iterable, Mapping, namedtuple
/usr/lib/python3/dist-packages/salt/utils/jinja.py:638: DeprecationWarning: Using or importing the ABCs from 'collections' instead of from 'collections.abc' is deprecated, and in 3.8 it will stop working
  if isinstance(lst1, collections.Hashable) and isinstance(lst2, collections.Hashable):
/usr/lib/python3/dist-packages/salt/utils/decorators/signature.py:31: DeprecationWarning: `formatargspec` is deprecated since Python 3.5. Use `signature` and the `Signature` object directly
  *salt.utils.args.get_function_argspec(original_function)
/usr/lib/python3/dist-packages/salt/utils/decorators/signature.py:31: DeprecationWarning: `formatargspec` is deprecated since Python 3.5. Use `signature` and the `Signature` object directly
  *salt.utils.args.get_function_argspec(original_function)
omv-data.local:
----------
          ID: refresh_pillar
    Function: salt.state
      Result: True
     Comment: States ran successfully. No changes made to omv-data.local.
     Started: 06:26:26.288797
    Duration: 215.527 ms
     Changes:
----------
          ID: run_state_deploy
    Function: salt.state
      Result: False
     Comment: Run failed on minions: omv-data.local
     Started: 06:26:26.504511
    Duration: 4050.61 ms
     Changes:
              omv-data.local:
                  Data failed to compile:
              ----------
                  Rendering SLS 'base:omv.deploy.cronapt.default' failed: Jinja error: Object of type StrictUndefined is not JSON serializable
              Traceback (most recent call last):
                File "/usr/lib/python3/dist-packages/salt/utils/templates.py", line 394, in render_jinja_tmpl
                  output = template.render(**decoded_context)
                File "/usr/lib/python3/dist-packages/jinja2/asyncsupport.py", line 76, in render
                  return original_render(self, *args, **kwargs)
                File "/usr/lib/python3/dist-packages/jinja2/environment.py", line 1008, in render
                  return self.environment.handle_exception(exc_info, True)
                File "/usr/lib/python3/dist-packages/jinja2/environment.py", line 780, in handle_exception
                  reraise(exc_type, exc_value, tb)
                File "/usr/lib/python3/dist-packages/jinja2/_compat.py", line 37, in reraise
                  raise value.with_traceback(tb)
                File "<template>", line 40, in top-level template code
                File "/usr/lib/python3/dist-packages/salt/utils/jinja.py", line 875, in format_json
                  json_txt = salt.utils.json.dumps(value, sort_keys=sort_keys, indent=indent).strip()
                File "/usr/lib/python3/dist-packages/salt/utils/json.py", line 145, in dumps
                  return json_module.dumps(obj, **kwargs)  # future lint: blacklisted-function
                File "/usr/lib/python3.7/json/__init__.py", line 238, in dumps
                  **kw).encode(obj)
                File "/usr/lib/python3.7/json/encoder.py", line 199, in encode
                  chunks = self.iterencode(o, _one_shot=True)
                File "/usr/lib/python3.7/json/encoder.py", line 257, in iterencode
                  return _iterencode(o, 0)
                File "/usr/lib/python3.7/json/encoder.py", line 179, in default
                  raise TypeError(f'Object of type {o.__class__.__name__} '
              TypeError: Object of type StrictUndefined is not JSON serializable


              ; line 40


              ---
              [...]
                  - source:
                    - salt://{{ tpldir }}/files/etc_cron-apt_config.j2
                  - template: jinja
                  - context:
                      email_config: {{ email_config | json }}
                      notification_config: {{ notification_config | json }}    <======================
                  - user: root
                  - group: root
                  - mode: 644


              Traceback (most recent call last):
              [...]
              ---


Summary for omv-data.local
------------
Succeeded: 1
Failed:    1
------------
Total states run:     2
Total run time:   4.266 s

Alles anzeigen

votdev · 11. März 2020

Zitat von Mobilis

I am having the same issue on two separate machines. I tried the two commands above and I still get the 502 Bad Gateway nginx page.

The first command appears to have succedded however, the second command had the following output.

Bash

root@omv-data:~# omv-salt stage run deploy
/usr/lib/python3/dist-packages/salt/modules/file.py:32: DeprecationWarning: Using or importing the ABCs from 'collections' instead of from 'collections.abc' is deprecated, and in 3.8 it will stop working
  from collections import Iterable, Mapping, namedtuple
/usr/lib/python3/dist-packages/salt/utils/jinja.py:638: DeprecationWarning: Using or importing the ABCs from 'collections' instead of from 'collections.abc' is deprecated, and in 3.8 it will stop working
  if isinstance(lst1, collections.Hashable) and isinstance(lst2, collections.Hashable):
/usr/lib/python3/dist-packages/salt/utils/decorators/signature.py:31: DeprecationWarning: `formatargspec` is deprecated since Python 3.5. Use `signature` and the `Signature` object directly
  *salt.utils.args.get_function_argspec(original_function)
/usr/lib/python3/dist-packages/salt/utils/decorators/signature.py:31: DeprecationWarning: `formatargspec` is deprecated since Python 3.5. Use `signature` and the `Signature` object directly
  *salt.utils.args.get_function_argspec(original_function)
omv-data.local:
----------
          ID: refresh_pillar
    Function: salt.state
      Result: True
     Comment: States ran successfully. No changes made to omv-data.local.
     Started: 06:26:26.288797
    Duration: 215.527 ms
     Changes:
----------
          ID: run_state_deploy
    Function: salt.state
      Result: False
     Comment: Run failed on minions: omv-data.local
     Started: 06:26:26.504511
    Duration: 4050.61 ms
     Changes:
              omv-data.local:
                  Data failed to compile:
              ----------
                  Rendering SLS 'base:omv.deploy.cronapt.default' failed: Jinja error: Object of type StrictUndefined is not JSON serializable
              Traceback (most recent call last):
                File "/usr/lib/python3/dist-packages/salt/utils/templates.py", line 394, in render_jinja_tmpl
                  output = template.render(**decoded_context)
                File "/usr/lib/python3/dist-packages/jinja2/asyncsupport.py", line 76, in render
                  return original_render(self, *args, **kwargs)
                File "/usr/lib/python3/dist-packages/jinja2/environment.py", line 1008, in render
                  return self.environment.handle_exception(exc_info, True)
                File "/usr/lib/python3/dist-packages/jinja2/environment.py", line 780, in handle_exception
                  reraise(exc_type, exc_value, tb)
                File "/usr/lib/python3/dist-packages/jinja2/_compat.py", line 37, in reraise
                  raise value.with_traceback(tb)
                File "<template>", line 40, in top-level template code
                File "/usr/lib/python3/dist-packages/salt/utils/jinja.py", line 875, in format_json
                  json_txt = salt.utils.json.dumps(value, sort_keys=sort_keys, indent=indent).strip()
                File "/usr/lib/python3/dist-packages/salt/utils/json.py", line 145, in dumps
                  return json_module.dumps(obj, **kwargs)  # future lint: blacklisted-function
                File "/usr/lib/python3.7/json/__init__.py", line 238, in dumps
                  **kw).encode(obj)
                File "/usr/lib/python3.7/json/encoder.py", line 199, in encode
                  chunks = self.iterencode(o, _one_shot=True)
                File "/usr/lib/python3.7/json/encoder.py", line 257, in iterencode
                  return _iterencode(o, 0)
                File "/usr/lib/python3.7/json/encoder.py", line 179, in default
                  raise TypeError(f'Object of type {o.__class__.__name__} '
              TypeError: Object of type StrictUndefined is not JSON serializable


              ; line 40


              ---
              [...]
                  - source:
                    - salt://{{ tpldir }}/files/etc_cron-apt_config.j2
                  - template: jinja
                  - context:
                      email_config: {{ email_config | json }}
                      notification_config: {{ notification_config | json }}    <======================
                  - user: root
                  - group: root
                  - mode: 644


              Traceback (most recent call last):
              [...]
              ---


Summary for omv-data.local
------------
Succeeded: 1
Failed:    1
------------
Total states run:     2
Total run time:   4.266 s

Alles anzeigen

Please execute the following commands and post the output.

Bash

# omv-confdbadm read --prettify conf.system.notification.notification
# omv-confdbadm read --prettify --filter '{"operator": "stringEquals", "arg0": "id", "arg1": "cronapt"}' conf.system.notification.notification

But i bet you won't be able to do that because your database is corrupted.

Mobilis · 17. März 2020

Zitat von votdev
Please execute the following commands and post the output.
Bash
# omv-confdbadm read --prettify conf.system.notification.notification
# omv-confdbadm read --prettify --filter '{"operator": "stringEquals", "arg0": "id", "arg1": "cronapt"}' conf.system.notification.notification
But i bet you won't be able to do that because your database is corrupted.

root@omv-data:~# omv-confdbadm read --prettify conf.system.notification.notification

[

{

"enable": true,

"id": "monitprocevents",

"uuid": "8bcb594f-0b99-47f1-bc63-390fe81019ba"

},

{

"enable": true,

"id": "monitloadavg",

"uuid": "dff60a4c-86c7-45e5-b666-aff4ed6a6726"

},

{

"enable": true,

"id": "monitmemoryusage",

"uuid": "7dd6bd1b-f8ee-4c04-a153-0b708b27dee9"

},

{

"enable": true,

"id": "monitcpuusage",

"uuid": "580c635f-14e2-4191-b2d7-aee5d296950c"

},

{

"enable": true,

"id": "monitfilesystems",

"uuid": "7ffc4f1a-0d25-4348-abe0-aeef5800b2e3"

},

{

"enable": true,

"id": "mdadm",

"uuid": "e012e293-e42f-49d7-88f8-43fa14337999"

},

{

"enable": true,

"id": "smartmontools",

"uuid": "04d8f06a-adae-4517-b31d-d8b68ccb90fc"

}

]

root@omv-data:~# omv-confdbadm read --prettify --filter '{"operator": "stringEquals", "arg0": "id", "arg1": "cronapt"}' conf.system.notification.notification

[]
Alles anzeigen

Thanks for you response I just noticed the forum was back up. Here is the results of the two command above.

PS: I can still access my shares just no UI.

Jimy · 17. März 2020

Zitat von votdev

You should log into the box via SSH or TTY and run one of the following commands:

omv-salt deploy run nginx (this module was marked dirty during the upgrade) or deploy the whole system with omv-salt stage run deploy.

After last update OMV 5 I cant get Web-gui with error: 502 bad gateway (nginx). Everything else seemed worked fine.After few days of strugling without forum you finally gave me solution! Second command of full deploy resolved my problem. Thanks once again.

votdev · 17. März 2020

Please run the following command omv-confdbadm migrate conf_0.5.8 to fix your database.

P.S.: It seems your system is really really old. Did you migrate it all the time from OMV 0.5?

Mobilis · 17. März 2020

Zitat von votdev

Please run the following command omv-confdbadm migrate conf_0.5.8 to fix your database.

P.S.: It seems your system is really really old. Did you migrate it all the time from OMV 0.5?

Didn't seem to like the command:

root@omv-data:~# omv-confdbadm migrate conf_0.5.8

usage: omv-confdbadm migrate [-h] id version

omv-confdbadm migrate: error: argument id: No valid data model ID.

root@omv-data:~#

I have been using OMV for a while but surely I haven't been updating since 0.5. To be honest I don't recall which version I started with. I do recall I have had to start from scratch several times.

votdev · 17. März 2020

Try omv-confdbadm migrate conf 0.5.8.

Mobilis · 17. März 2020

Zitat von votdev

Try omv-confdbadm migrate conf 0.5.8.

root@omv-data:~# omv-confdbadm migrate conf 0.5.8

Running migration conf_0.5.8

Running migration conf_0.5.15

WARNING: The node 'transferlog' already exists at XPath '/config/services/ftp'.

Running migration conf_0.5.26

WARNING: The node 'apt' already exists at XPath '/config/system'.

WARNING: The node 'distribution' already exists at XPath '/config/system/apt'.

WARNING: The node 'proposed' already exists at XPath '/config/system/apt/distribution'.

WARNING: The node 'partner' already exists at XPath '/config/system/apt/distribution'.

Running migration conf_0.5.39

WARNING: The node 'monitor' already exists at XPath '/config/services/smart'.

Running migration conf_0.6

WARNING: The node 'audit' already exists at XPath '/config/services/smb/shares/share'.

Running migration conf_0.6.11

WARNING: The node 'enable' already exists at XPath '/config/services/smb/shares/share'.

Running migration conf_0.6.12

Running migration conf_1.0.12

Running migration conf_1.0.24

Running migration conf_1.0.26

WARNING: The node 'hidden' already exists at XPath '/config/system/fstab/mntent'.

Running migration conf_1.0.29

WARNING: The node 'pubkeyauthentication' already exists at XPath '/config/services/ssh'.

Running migration conf_1.2

Running migration conf_1.9

Running migration conf_2.0.4

Running migration conf_2.0.6

WARNING: The node 'monitoring' already exists at XPath '/config/system'.

WARNING: The node 'perfstats' already exists at XPath '/config/system/monitoring'.

WARNING: The node 'enable' already exists at XPath '/config/system/monitoring/perfstats'.

Running migration conf_2.0.8

Running migration conf_3.0.9

Running migration conf_3.0.11

Running migration conf_3.0.12

WARNING: The node 'proxy' already exists at XPath '/config/system/network'.

WARNING: The node 'http' already exists at XPath '/config/system/network/proxy'.

WARNING: The node 'enable' already exists at XPath '/config/system/network/proxy/http'.

WARNING: The node 'host' already exists at XPath '/config/system/network/proxy/http'.

WARNING: The node 'port' already exists at XPath '/config/system/network/proxy/http'.

WARNING: The node 'username' already exists at XPath '/config/system/network/proxy/http'.

WARNING: The node 'password' already exists at XPath '/config/system/network/proxy/http'.

WARNING: The node 'https' already exists at XPath '/config/system/network/proxy'.

WARNING: The node 'enable' already exists at XPath '/config/system/network/proxy/https'.

WARNING: The node 'host' already exists at XPath '/config/system/network/proxy/https'.

WARNING: The node 'port' already exists at XPath '/config/system/network/proxy/https'.

WARNING: The node 'username' already exists at XPath '/config/system/network/proxy/https'.

WARNING: The node 'password' already exists at XPath '/config/system/network/proxy/https'.

WARNING: The node 'ftp' already exists at XPath '/config/system/network/proxy'.

WARNING: The node 'enable' already exists at XPath '/config/system/network/proxy/ftp'.

WARNING: The node 'host' already exists at XPath '/config/system/network/proxy/ftp'.

WARNING: The node 'port' already exists at XPath '/config/system/network/proxy/ftp'.

WARNING: The node 'username' already exists at XPath '/config/system/network/proxy/ftp'.

WARNING: The node 'password' already exists at XPath '/config/system/network/proxy/ftp'.

Running migration conf_3.0.15

WARNING: The node 'dns' already exists at XPath '/config/system/network'.

WARNING: The node 'hostname' already exists at XPath '/config/system/network/dns'.

WARNING: The node 'domainname' already exists at XPath '/config/system/network/dns'.

Running migration conf_3.0.23

Running migration conf_3.0.37

Running migration conf_3.0.38

Running migration conf_3.0.68

Running migration conf_4.0.6

Running migration conf_4.0.17

Running migration conf_5.0.0

WARNING: The node 'timemachine' already exists at XPath '/config/services/smb/shares/share'.

Running migration conf_5.0.3

Running migration conf_5.2.0

Mobilis · 18. März 2020

Then I ran the following command and I was back in business.

omv-salt stage run deploy

Jetzt mitmachen!