netbox and netbox-rq services activating auto-restart

[MinervaPaoletti]

Hello,

We have a version netbox 2.5.3 with database v.9.6 install on debian 9.
I want to migrate this install a same version or a version below in order to do a import to my database on my last OS debian 11
So I create a new virtual machine on my ESXi, I installed as PostgreSQL Database 9.6, Redis 3.2.6 with python 3.6.0.
All package works I have trouble with gunicorn.
When I install netbox the folder crontrib don't exist so I do copy of this file because of when I lauch this comma,nd line sudo systemctl start netbox netbox-rq the service is not active

● netbox.service - NetBox WSGI Service Loaded: loaded (/etc/systemd/system/netbox.service; enabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Wed 2023-09-20 10:24:27 CEST; 25s ago Docs: https://docs.netbox.dev/ Process: 921789 ExecStart=/usr/local/bin/gunicorn --pid /var/tmp/netbox.pid --pythonpath /opt/netbox/netbox --config /o> Main PID: 921789 (code=exited, status=1/FAILURE) CPU: 103ms

I use ChaTGPT Bard in order to my issue but nothing for resolv my issue I read many discussion I try many command line on this discussion but not working

Someone can help me ?

Sorry in oder to my spelling mistake I'm French I hope you undertand me
Thanks

[candlerb]

Your first point of call is to run journalctl -eu netbox to see what errors are being generated.

But I can tell you that you're going to have problems with such an old version: 2.5.3 was released in January 2019.

Firstly, I see you're trying to run /usr/local/bin/gunicorn. Netbox is normally run from within its own virtualenv, which today means you must run /opt/netbox/venv/bin/gunicorn. There is an example netbox.service here.

However, the virtualenv was not made part of standard installs until Feb 2020:

commit 0851b97ba5445583a9c8452009b5b45a2e9f110e
Author: Jeremy Stretch <[email protected]>
Date:   Wed Feb 26 13:54:07 2020 -0500

    Update the upgrade script & instructions to use a virtual environment

Prior to that it would have been a hit-and-miss of installing global pip packages which may or may not interfere with the system python packages you have.

Secondly, (re)installing old versions of Netbox is prone to problems. Netbox never fully pinned its package version requirements, which means it's not repeatable to install. v2.5.3 may have installed successfully nearly 5 years ago, but today it may pull in a different and incompatible set of dependencies. If this affects you, then run pip freeze on the existing 2.5.3 system you have, and use its output to control the requirements when you're creating the new system. Again, if you're not doing this with a virtualenv, it's likely to be a mess.

However, do note that you can take a Netbox 2.5.3 database and import it into any version up to and including Netbox 2.11.12. After restoring you need to run upgrade.sh to apply migrations to bring the schema up to date. So you don't have to stay on this older version, except that there are API changes which may affect any existing integrations you have already created.

Once you are on 2.11.12 then you can export the database again and then import into any current version, including the latest 3.6.1.

I'd strongly recommend you aim to do this, rather than try to keep the 5-year-old software running.

[candlerb]

You first need to export your database, install Netbox v2.11.12 somewhere, import your database into that, then ./upgrade.sh and check it's working.

Once you've done that, you can repeat the process: export the database, install Netbox v3.6.5 somewhere, import the database, then ./upgrade.sh

Netbox v2.11.12 may not run with anything later than python 3.8, but Netbox v3.6.5 needs at least python 3.8. You could run two different VMs to make this easier. I suggest Ubuntu 20.04 for the v2.11.12 machine, and Ubuntu 22.04 for the final v3.6.5 machine.

Postgres should import a dump taken from an older version of Postgres. Don't copy the underlying database files; do an export and import. This is documented here.

Also read the general upgrade instructions and all the vX.X.0 release notes for the intervening versions.

[MinervaPaoletti]

Thanks a lot to reply me 👍 .
I will install Netbox v2.11.12 on Debian 11 with Python3.7 ,Redis 6.0.
I have question in order to Postgres :
For do a import of my database in my netbox 2.11, I need a higher version Postgres 9.6 is this correct ?

PS : When you said anything later than python 3.8, it's <3.8 ou <=3.8 ?

Thanks

[MinervaPaoletti]

Hello Candlerb,

I installed the Python 3.7, Redis 6.0 and Postgres 12.17 packages on my Debian 11.
To import my database I followed this tutorial:
https://www.reddit.com/r/networking/comments/ms5p2e/netbox_import_database_on_new_install/
I stopped at point 5 then tried to do an upgrade.sh with the following command
sudo PYTHON=/usr/local/bin/python3.7 /opt/netbox/upgrade.sh
But I got an error message during installation

AttributeError: 'EntryPoints' object has no attribute 'get'

When I look at the error message on the Internet I don't have the package importlib-metadata-4.13.0
So I installed it and Entrypoints but I got the same message. Do you have any ideas please?

THANKS

[candlerb]

But I got an error message during installation

Without seeing the full output including backtrace, that error doesn't really mean anything.

I suspect you'll have to freeze your packages: temporarily replace requirements.txt with the 2.11.12 one from here.

I wouldn't follow random stuff you find on reddit. The sequence is:

1. Install a fresh Netbox 2.11.12. There are no hacks required apart from possibly the requirements.txt. ./upgrade.sh should be successful; if not, report the full error. Test that it works (e.g. create a device site, create an IP address)
2. Now export your postgres database from the old database, import it into the new one, and re-run ./upgrade.sh. Since it's installing exactly the same packages, if it worked in step (1) it should work again. Test.

[MinervaPaoletti]

Really thanks you a lot to help me.
I will tried.

PS : question : When you said anything later than python 3.8, It's <3.8 ou <=3.8 ?

[MinervaPaoletti]

Hello,
Someone can I help me please ?

thanks

[candlerb]

PS : When you said anything later than python 3.8, it's <3.8 ou <=3.8 ?

3.8 is fine. IIRC, Netbox 2.11 works with Python 3.6 to 3.8 inclusive. Higher versions may or may not work.

[candlerb]

You didn't show the responses to those commands, but clearly dbnetbox and netbox are two different databases.

[MinervaPaoletti]

Hello,
Yes, dbnetbox and netbox are different because I would change a name to my database and user of this website
https://docs.netbox.dev/en/stable/installation/1-postgresql/
This is my command for delete and import my database :

sudo -u postgres psql

postgres=# \l
                                  Liste des bases de données
    Nom    | Propriétaire | Encodage | Collationnement | Type caract. |    Droits d'accès
-----------+--------------+----------+-----------------+--------------+-----------------------
 dbnetbox  | postgres     | UTF8     | fr_FR.UTF-8     | fr_FR.UTF-8  | =Tc/postgres         +
           |              |          |                 |              | postgres=CTc/postgres+
           |              |          |                 |              | srt=CTc/postgres
 postgres  | postgres     | UTF8     | fr_FR.UTF-8     | fr_FR.UTF-8  |
 template0 | postgres     | UTF8     | fr_FR.UTF-8     | fr_FR.UTF-8  | =c/postgres          +
           |              |          |                 |              | postgres=CTc/postgres
 template1 | postgres     | UTF8     | fr_FR.UTF-8     | fr_FR.UTF-8  | =c/postgres          +
           |              |          |                 |              | postgres=CTc/postgres
(4 lignes)

postgres=# DROP DATABASE IF EXISTS dbnetbox;

postgres=# \l
                                  Liste des bases de données
    Nom    | Propriétaire | Encodage | Collationnement | Type caract. |    Droits d'accès
-----------+--------------+----------+-----------------+--------------+-----------------------
 postgres  | postgres     | UTF8     | fr_FR.UTF-8     | fr_FR.UTF-8  |
 template0 | postgres     | UTF8     | fr_FR.UTF-8     | fr_FR.UTF-8  | =c/postgres          +
           |              |          |                 |              | postgres=CTc/postgres
 template1 | postgres     | UTF8     | fr_FR.UTF-8     | fr_FR.UTF-8  | =c/postgres          +
           |              |          |                 |              | postgres=CTc/postgres
(3 lignes)

postgres=# CREATE DATABASE netbox;
CREATE DATABASE
postgres=#psql netbox < /opt/sauv_netbox_131223.sql

Next I give all privileges on database

postgres=# GRANT ALL PRIVILEGES ON DATABASE netbox To netbox;

And I change my files configuration.py with a good information on my database
I launch sudo PYTHON=/usr/local/bin/python3.8 /opt/netbox/upgrade.sh
This migrate works this time

Operations to perform:
  Apply all migrations: admin, auth, circuits, contenttypes, dcim, extras, ipam, secrets, sessions, taggit, tenancy, users, virtualization
Running migrations:
  Applying contenttypes.0001_initial... OK
  Applying auth.0001_initial... OK
  Applying admin.0001_initial... OK
  Applying admin.0002_logentry_remove_auto_add... OK
  Applying admin.0003_logentry_add_action_flag_choices... OK
  Applying contenttypes.0002_remove_content_type_name... OK
  Applying auth.0002_alter_permission_name_max_length... OK
  Applying auth.0003_alter_user_email_max_length... OK
  Applying auth.0004_alter_user_username_opts... OK
  Applying auth.0005_alter_user_last_login_null... OK
  Applying auth.0006_require_contenttypes_0002... OK
  Applying auth.0007_alter_validators_add_error_messages... OK
  Applying auth.0008_alter_user_username_max_length... OK
  Applying auth.0009_alter_user_last_name_max_length... OK
  Applying auth.0010_alter_group_name_max_length... OK
  Applying auth.0011_update_proxy_permissions... OK
  Applying auth.0012_alter_user_first_name_max_length... OK
  Applying tenancy.0001_initial... OK
  Applying tenancy.0002_tenant_group_optional... OK
  Applying tenancy.0003_unicode_literals... OK
  Applying dcim.0001_initial... OK
  Applying ipam.0001_initial... OK
  Applying ipam.0002_vrf_add_enforce_unique... OK
  Applying dcim.0002_auto_20160622_1821... OK
  Applying dcim.0003_auto_20160628_1721... OK
  Applying dcim.0004_auto_20160701_2049... OK
  Applying dcim.0005_auto_20160706_1722... OK
  Applying dcim.0006_add_device_primary_ip4_ip6... OK
  Applying dcim.0007_device_copy_primary_ip... OK
  Applying dcim.0008_device_remove_primary_ip... OK
  Applying dcim.0009_site_32bit_asn_support... OK
  Applying dcim.0010_devicebay_installed_device_set_null... OK
  Applying ipam.0003_ipam_add_vlangroups... OK
  Applying ipam.0004_ipam_vlangroup_uniqueness... OK
  Applying ipam.0005_auto_20160725_1842... OK
  Applying ipam.0006_vrf_vlan_add_tenant... OK
  Applying ipam.0007_prefix_ipaddress_add_tenant... OK
  Applying ipam.0008_prefix_change_order... OK
  Applying ipam.0009_ipaddress_add_status... OK
  Applying ipam.0010_ipaddress_help_texts... OK
  Applying ipam.0011_rir_add_is_private... OK
  Applying dcim.0011_devicetype_part_number... OK
  Applying dcim.0012_site_rack_device_add_tenant... OK
  Applying dcim.0013_add_interface_form_factors... OK
  Applying dcim.0014_rack_add_type_width... OK
  Applying dcim.0015_rack_add_u_height_validator... OK
  Applying dcim.0016_module_add_manufacturer... OK
  Applying dcim.0017_rack_add_role... OK
  Applying dcim.0018_device_add_asset_tag... OK
  Applying dcim.0019_new_iface_form_factors... OK
  Applying dcim.0020_rack_desc_units... OK
  Applying dcim.0021_add_ff_flexstack... OK
  Applying dcim.0022_color_names_to_rgb... OK
  Applying ipam.0012_services... OK
  Applying ipam.0013_prefix_add_is_pool... OK
  Applying ipam.0014_ipaddress_status_add_deprecated... OK
  Applying ipam.0015_global_vlans... OK
  Applying ipam.0016_unicode_literals... OK
  Applying ipam.0017_ipaddress_roles... OK
  Applying ipam.0018_remove_service_uniqueness_constraint... OK
  Applying dcim.0023_devicetype_comments... OK
  Applying dcim.0024_site_add_contact_fields... OK
  Applying dcim.0025_devicetype_add_interface_ordering... OK
  Applying dcim.0026_add_rack_reservations... OK
  Applying dcim.0027_device_add_site... OK
  Applying dcim.0028_device_copy_rack_to_site... OK
  Applying dcim.0029_allow_rackless_devices... OK
  Applying dcim.0030_interface_add_lag... OK
  Applying dcim.0031_regions... OK
  Applying dcim.0032_device_increase_name_length... OK
  Applying dcim.0033_rackreservation_rack_editable... OK
  Applying dcim.0034_rename_module_to_inventoryitem... OK
  Applying dcim.0035_device_expand_status_choices... OK
  Applying dcim.0036_add_ff_juniper_vcp... OK
  Applying dcim.0037_unicode_literals... OK
  Applying dcim.0038_wireless_interfaces... OK
  Applying dcim.0039_interface_add_enabled_mtu... OK
  Applying dcim.0040_inventoryitem_add_asset_tag_description... OK
  Applying dcim.0041_napalm_integration... OK
  Applying dcim.0042_interface_ff_10ge_cx4... OK
  Applying dcim.0043_device_component_name_lengths... OK
  Applying virtualization.0001_virtualization... OK
  Applying virtualization.0002_virtualmachine_add_status... OK
  Applying dcim.0044_virtualization... OK
  Applying virtualization.0003_cluster_add_site... OK
  Applying virtualization.0004_virtualmachine_add_role... OK
  Applying virtualization.0005_django2... OK
  Applying taggit.0001_initial... OK
  Applying taggit.0002_auto_20150616_2121... OK
  Applying virtualization.0006_tags... OK
  Applying virtualization.0007_change_logging... OK
  Applying virtualization.0008_virtualmachine_local_context_data... OK
  Applying tenancy.0004_tags... OK
  Applying tenancy.0005_change_logging... OK
  Applying extras.0001_initial... OK
  Applying extras.0002_custom_fields... OK
  Applying extras.0003_exporttemplate_add_description... OK
  Applying extras.0004_topologymap_change_comma_to_semicolon... OK
  Applying extras.0005_useraction_add_bulk_create... OK
  Applying extras.0006_add_imageattachments... OK
  Applying extras.0007_unicode_literals... OK
  Applying extras.0008_reports... OK
  Applying extras.0009_topologymap_type... OK
  Applying extras.0010_customfield_filter_logic... OK
  Applying extras.0011_django2... OK
  Applying extras.0012_webhooks... OK
  Applying extras.0013_objectchange... OK
  Applying ipam.0019_virtualization... OK
  Applying ipam.0020_ipaddress_add_role_carp... OK
  Applying dcim.0045_devicerole_vm_role... OK
  Applying dcim.0046_rack_lengthen_facility_id... OK
  Applying dcim.0047_more_100ge_form_factors... OK
  Applying dcim.0048_rack_serial... OK
  Applying dcim.0049_rackreservation_change_user... OK
  Applying dcim.0050_interface_vlan_tagging... OK
  Applying dcim.0051_rackreservation_tenant... OK
  Applying dcim.0052_virtual_chassis... OK
  Applying dcim.0053_platform_manufacturer... OK
  Applying dcim.0054_site_status_timezone_description... OK
  Applying dcim.0055_virtualchassis_ordering... OK
  Applying dcim.0056_django2... OK
  Applying dcim.0057_tags... OK
  Applying dcim.0058_relax_rack_naming_constraints... OK
  Applying dcim.0059_site_latitude_longitude... OK
  Applying dcim.0060_change_logging... OK
  Applying dcim.0061_platform_napalm_args... OK
  Applying extras.0014_configcontexts... OK
  Applying extras.0015_remove_useraction... OK
  Applying extras.0016_exporttemplate_add_cable... OK
  Applying extras.0017_exporttemplate_mime_type_length... OK
  Applying extras.0018_exporttemplate_add_jinja2... OK
  Applying extras.0019_tag_taggeditem... OK
  Applying virtualization.0009_custom_tag_models... OK
  Applying virtualization.0010_cluster_add_tenant... OK
  Applying virtualization.0011_3569_virtualmachine_fields... OK
  Applying tenancy.0006_custom_tag_models... OK
  Applying virtualization.0012_vm_name_nonunique... OK
  Applying virtualization.0013_deterministic_ordering... OK
  Applying virtualization.0014_standardize_description... OK
  Applying ipam.0021_vrf_ordering... OK
  Applying ipam.0022_tags... OK
  Applying ipam.0023_change_logging... OK
  Applying ipam.0024_vrf_allow_null_rd... OK
  Applying ipam.0025_custom_tag_models... OK
  Applying ipam.0026_prefix_ordering_vrf_nulls_first... OK
  Applying ipam.0027_ipaddress_add_dns_name... OK
  Applying ipam.0028_3569_prefix_fields... OK
  Applying ipam.0029_3569_ipaddress_fields... OK
  Applying ipam.0030_3569_vlan_fields... OK
  Applying ipam.0031_3569_service_fields... OK
  Applying ipam.0032_role_description... OK
  Applying ipam.0033_deterministic_ordering... OK
  Applying ipam.0034_fix_ipaddress_status_dhcp... OK
  Applying ipam.0035_drop_ip_family... OK
  Applying ipam.0036_standardize_description... OK
  Applying secrets.0001_initial... OK
  Applying secrets.0002_userkey_add_session_key... OK
  Applying secrets.0003_unicode_literals... OK
  Applying secrets.0004_tags... OK
  Applying secrets.0005_change_logging... OK
  Applying secrets.0006_custom_tag_models... OK
  Applying dcim.0062_interface_mtu... OK
  Applying dcim.0063_device_local_context_data... OK
  Applying dcim.0064_remove_platform_rpc_client... OK
  Applying dcim.0065_front_rear_ports... OK
  Applying circuits.0001_initial... OK
  Applying circuits.0002_auto_20160622_1821... OK
  Applying circuits.0003_provider_32bit_asn_support... OK
  Applying circuits.0004_circuit_add_tenant... OK
  Applying circuits.0005_circuit_add_upstream_speed... OK
  Applying circuits.0006_terminations... OK
  Applying dcim.0066_cables...
    Adding console connections... 0 cables created
    Adding power connections... 0 cables created
    Adding interface connections... 0 cables created
 OK
  Applying dcim.0067_device_type_remove_qualifiers... OK
  Applying dcim.0068_rack_new_fields... OK
  Applying dcim.0069_deprecate_nullablecharfield... OK
  Applying dcim.0070_custom_tag_models... OK
  Applying circuits.0007_circuit_add_description... OK
  Applying circuits.0008_circuittermination_interface_protect_on_delete... OK
  Applying circuits.0009_unicode_literals... OK
  Applying circuits.0010_circuit_status... OK
  Applying circuits.0011_tags... OK
  Applying circuits.0012_change_logging... OK
  Applying circuits.0013_cables...
    Adding circuit terminations... 0 cables created
 OK
  Applying circuits.0014_circuittermination_description... OK
  Applying circuits.0015_custom_tag_models... OK
  Applying extras.0020_tag_data... OK
  Applying extras.0021_add_color_comments_changelog_to_tag... OK
  Applying extras.0022_custom_links... OK
  Applying extras.0023_fix_tag_sequences... OK
  Applying extras.0024_scripts... OK
  Applying extras.0025_objectchange_time_index... OK
  Applying extras.0026_webhook_ca_file_path... OK
  Applying extras.0027_webhook_additional_headers... OK
  Applying extras.0028_remove_topology_maps... OK
  Applying extras.0029_3569_customfield_fields... OK
  Applying extras.0030_3569_objectchange_fields... OK
  Applying extras.0031_3569_exporttemplate_fields... OK
  Applying extras.0032_3569_webhook_fields... OK
  Applying extras.0033_graph_type_template_language... OK
  Applying extras.0034_configcontext_tags... OK
  Applying extras.0035_deterministic_ordering... OK
  Applying extras.0036_contenttype_filters_to_q_objects... OK
  Applying extras.0037_configcontexts_clusters... OK
  Applying extras.0038_webhook_template_support... OK
  Applying extras.0039_update_features_content_types... OK
  Applying extras.0040_standardize_description... OK
  Applying extras.0041_tag_description... OK
  Applying extras.0042_customfield_manager... OK
  Applying virtualization.0015_vminterface... OK
  Applying ipam.0037_ipaddress_assignment... OK
  Applying dcim.0071_device_components_add_description... OK
  Applying dcim.0072_powerfeeds... OK
  Applying dcim.0073_interface_form_factor_to_type... OK
  Applying dcim.0074_increase_field_length_platform_name_slug... OK
  Applying dcim.0075_cable_devices...
Updating cable device terminations...
 OK
  Applying dcim.0076_console_port_types... OK
  Applying dcim.0077_power_types... OK
  Applying dcim.0078_3569_site_fields... OK
  Applying dcim.0079_3569_rack_fields... OK
  Applying dcim.0080_3569_devicetype_fields... OK
  Applying dcim.0081_3569_device_fields... OK
  Applying dcim.0082_3569_interface_fields... OK
  Applying virtualization.0016_replicate_interfaces...
    Replicating 0 VM interfaces...
    Replicating assigned objects...
 OK
  Applying virtualization.0017_update_jsonfield... OK
  Applying virtualization.0018_custom_field_data... OK
  Applying tenancy.0007_nested_tenantgroups... OK
  Applying tenancy.0008_nested_tenantgroups_rebuild... OK
  Applying tenancy.0009_standardize_description... OK
  Applying tenancy.0010_custom_field_data... OK
  Applying users.0001_api_tokens... OK
  Applying users.0002_unicode_literals... OK
  Applying users.0003_token_permissions... OK
  Applying users.0004_standardize_description... OK
  Applying users.0005_userconfig... OK
  Applying users.0006_create_userconfigs... OK
  Applying users.0007_proxy_group_user... OK
  Applying users.0008_objectpermission... OK
  Applying users.0009_replicate_permissions... OK
  Applying secrets.0007_secretrole_description... OK
  Applying secrets.0008_standardize_description... OK
  Applying secrets.0009_secretrole_drop_users_groups... OK
  Applying secrets.0010_custom_field_data... OK
  Applying ipam.0038_custom_field_data... OK
  Applying extras.0043_report... OK
  Applying extras.0044_jobresult... OK
  Applying extras.0045_configcontext_changelog... OK
  Applying extras.0046_update_jsonfield... OK
  Applying extras.0047_tag_ordering... OK
  Applying extras.0048_exporttemplate_remove_template_language... OK
  Applying extras.0049_remove_graph... OK
  Applying extras.0050_customfield_changes... OK
  Applying dcim.0082_3569_port_fields... OK
  Applying dcim.0083_3569_cable_fields... OK
  Applying dcim.0084_3569_powerfeed_fields... OK
  Applying dcim.0085_3569_poweroutlet_fields... OK
  Applying dcim.0086_device_name_nonunique... OK
  Applying dcim.0087_role_descriptions... OK
  Applying dcim.0088_powerfeed_available_power... OK
  Applying dcim.0089_deterministic_ordering... OK
  Applying dcim.0090_cable_termination_models... OK
  Applying dcim.0091_interface_type_other... OK
  Applying dcim.0092_fix_rack_outer_unit... OK
  Applying dcim.0093_device_component_ordering... OK
  Applying dcim.0094_device_component_template_ordering... OK
  Applying dcim.0095_primary_model_ordering... OK
  Applying dcim.0096_interface_ordering... OK
  Applying dcim.0097_interfacetemplate_type_other... OK
  Applying dcim.0098_devicetype_images... OK
  Applying dcim.0099_powerfeed_negative_voltage... OK
  Applying dcim.0100_mptt_remove_indexes... OK
  Applying dcim.0101_nested_rackgroups... OK
  Applying dcim.0102_nested_rackgroups_rebuild... OK
  Applying dcim.0103_standardize_description... OK
  Applying dcim.0104_correct_infiniband_types... OK
  Applying dcim.0105_interface_name_collation... OK
  Applying dcim.0106_role_default_color... OK
  Applying dcim.0107_component_labels... OK
  Applying dcim.0108_add_tags... OK
  Applying dcim.0109_interface_remove_vm... OK
  Applying dcim.0110_virtualchassis_name... OK
  Applying dcim.0111_component_template_description... OK
  Applying dcim.0112_standardize_components... OK
  Applying dcim.0113_nullbooleanfield_to_booleanfield... OK
  Applying dcim.0114_update_jsonfield... OK
  Applying dcim.0115_rackreservation_order... OK
  Applying dcim.0116_rearport_max_positions... OK
  Applying dcim.0117_custom_field_data... OK
  Applying circuits.0016_3569_circuit_fields... OK
  Applying circuits.0017_circuittype_description... OK
  Applying circuits.0018_standardize_description... OK
  Applying circuits.0019_nullbooleanfield_to_booleanfield... OK
  Applying circuits.0020_custom_field_data... OK
  Applying extras.0051_migrate_customfields... OK
  Applying extras.0052_customfield_cleanup... OK
  Applying extras.0053_rename_webhook_obj_type... OK
  Applying extras.0054_standardize_models... OK
  Applying extras.0055_objectchange_data... OK
  Applying dcim.0118_inventoryitem_mptt... OK
  Applying dcim.0119_inventoryitem_mptt_rebuild... OK
  Applying dcim.0120_cache_cable_peer...
    Updating console port cable peers...
    Updating console server port cable peers...
    Updating power port cable peers...
    Updating power outlet cable peers...
    Updating interface cable peers...
    Updating front port cable peers...
    Updating rear port cable peers...
    Updating power feed cable peers...
 OK
  Applying dcim.0121_cablepath... OK
  Applying dcim.0122_standardize_name_length... OK
  Applying dcim.0123_standardize_models... OK
  Applying dcim.0124_mark_connected... OK
  Applying dcim.0125_console_port_speed... OK
  Applying dcim.0126_rename_rackgroup_location... OK
  Applying dcim.0127_device_location... OK
  Applying dcim.0128_device_location_populate... OK
  Applying dcim.0129_interface_parent... OK
  Applying dcim.0130_sitegroup... OK
  Applying extras.0056_extend_configcontext... OK
  Applying extras.0057_customlink_rename_fields... OK
  Applying extras.0058_journalentry... OK
  Applying circuits.0021_cache_cable_peer...
    Updating circuit termination cable peers...
 OK
  Applying circuits.0022_cablepath... OK
  Applying circuits.0023_circuittermination_port_speed_optional... OK
  Applying circuits.0024_standardize_name_length... OK
  Applying circuits.0025_standardize_models... OK
  Applying circuits.0026_mark_connected... OK
  Applying circuits.0027_providernetwork... OK
  Applying circuits.0028_cache_circuit_terminations...
    Caching circuit terminations...
 OK
  Applying circuits.0029_circuit_tracing... OK
  Applying dcim.0131_consoleport_speed... OK
  Applying extras.0059_exporttemplate_as_attachment... OK
  Applying tenancy.0011_standardize_name_length... OK
  Applying ipam.0039_service_ports_array... OK
  Applying ipam.0040_service_drop_port... OK
  Applying ipam.0041_routetarget... OK
  Applying ipam.0042_standardize_name_length... OK
  Applying ipam.0043_add_tenancy_to_aggregates... OK
  Applying ipam.0044_standardize_models... OK
  Applying ipam.0045_vlangroup_scope... OK
  Applying ipam.0046_set_vlangroup_scope_types... OK
  Applying ipam.0047_prefix_depth_children... OK
  Applying ipam.0048_prefix_populate_depth_children...
Updating 0 prefixes...
 OK
  Applying secrets.0011_secret_generic_assignments... OK
  Applying secrets.0012_standardize_name_length... OK
  Applying secrets.0013_standardize_models... OK
  Applying sessions.0001_initial... OK
  Applying taggit.0003_taggeditem_add_unique_index... OK
  Applying tenancy.0012_standardize_models... OK
  Applying users.0010_update_jsonfield... OK
  Applying users.0011_standardize_models... OK
  Applying virtualization.0019_standardize_name_length... OK
  Applying virtualization.0020_standardize_models... OK
  Applying virtualization.0021_virtualmachine_vcpus_decimal... OK
  Applying virtualization.0022_vminterface_parent... OK
  Applying virtualization.0023_virtualmachine_natural_ordering... OK
Checking for missing cable paths (python3 netbox/manage.py trace_paths --no-input)...
Found no missing console port paths; skipping
Found no missing console server port paths; skipping
Found no missing interface paths; skipping
Found no missing power feed paths; skipping
Found no missing power outlet paths; skipping
Found no missing power port paths; skipping
Finished.
Collecting static files (python3 netbox/manage.py collectstatic --no-input)...

202 static files copied to '/opt/netbox-2.11.12/netbox/static', 755 unmodified.
Removing stale content types (python3 netbox/manage.py remove_stale_contenttypes --no-input)...
Removing expired user sessions (python3 netbox/manage.py clearsessions)...
Clearing cache data (python3 netbox/manage.py invalidate all)...
Upgrade complete! Don't forget to restart the NetBox services:
  > sudo systemctl restart netbox netbox-rq

I tried to connect to my environment via the GUI but my account of my version netbox 2.5.3 with database v.9.6 install on debian 9 does not work and the admin account too.
I created another admin account via the command: python3 manage.py createsuperuser when I connect I have no object unfortunately.
I guess a create a new post because my service netbox and netbox-rq services works.
Now I have a trouble in order to find my items , my objetcs and my configuration on my new setup because this migrate works.
I have just a question : if I migrate my database I have to find all my configuration (my accounts, objects, etc.) it works like this I'm right.

[MinervaPaoletti]

@candlerb Happy New Years
do you think that there is a problem in my process. I asked myself the question theoretically when I do the command psql -c 'drop database dbnetbox' my database is not deleted I have to do it postgres=# DROP DATABASE IF EXISTS dbnetbox; to delete my database is this good?

PS: is this the right account to go into postgres sudo -u postgres psql
THANKS

[candlerb]

I have just a question : if I migrate my database I have to find all my configuration (my accounts, objects, etc.) it works like this I'm right.

I don't understand the question.

In Django, a "migration" is a set of schema changes to be applied, i.e. create tables, create columns etc. Some migrations also modify data so that it fits into the new schema. You don't have to "find" anything.

when I do the command psql -c 'drop database dbnetbox' my database is not deleted

So what does happen? Nothing? Do you get an error? If so, what does the error say? Without seeing the error, I can't tell what might have gone wrong. It's correct that you that you can't drop a non-existent database though, and "drop database if exists" is fine.

Note that

sudo -u postgres psql

can be used to create the netbox database and user, but if you want to do work inside the (db)netbox database then you should select the database:

sudo -u postgres psql dbnetbox

PS: is this the right account to go into postgres sudo -u postgres psql

If you are on Debian or Ubuntu then that's right - and also it's what the Netbox documentation says.

[MinervaPaoletti]

I have just a question : if I migrate my database I have to find all my configuration (my accounts, objects, etc.) it works like this I'm right.

my initial plan is to be able to migrate my netbox 2.5.3 version with a 9.6 database to Debian 11.
By doing this migration or update I want to recover my sites, my tenants, my vlans and my connection accounts, etc.... without doing a CSV import from the GUI.

Today I am with a version of netbox 2.11 and Postgres 12.17 on Debian 11.
If I migrate (export/import) my Postgres 9.6 database to my new machine, do I have access to my entire configuration?

quand j'exécute la commande, psql -c 'drop database dbnetbox'ma base de données n'est pas supprimée
I will keep you informed for the rest I will try again

[MinervaPaoletti]

D,
I am closing because I no longer have a service problem but see post #15744 if necessary in the event of a problem migrating from an old version of netbox to a new OS.
Thanks