Error Applying MR66.SQL – ERROR 1060 (42S21) at line 3: Duplicate column name

[Sergio]

Like it

Up

0

Down

Drop it

::

Hello,

How did you upgrade the console?

Did you used the rpm package?

Kind regards,

Sergio B.

[JonRussell]

Like it

Up

0

Down

Drop it

::

I ran yum update using ansible. I’ve just noticed in the ansible logs there is a different error. Similar to the last mr65 one. See below.

"66: (MR:66) 1071: Specified key was too long; max key length is 767 bytes
ALTER TABLE talert_actions ADD CONSTRAINT UNIQUE (name)"

Shall I try the same fix?

SET SESSION innodb_strict_mode=OFF

Thanks.

Resolving Dependencies
--> Running transaction check
---> Package pandorafms_console.noarch 0:7.0NG.773.3-1 will be updated
---> Package pandorafms_console.x86_64 0:7.0NG.774-231121 will be an update
---> Package pandorafms_server.noarch 0:7.0NG.773.3-1 will be updated
---> Package pandorafms_server.x86_64 0:7.0NG.774-231121 will be an update
--> Finished Dependency Resolution
Dependencies Resolved
================================================================================
 Package               Arch      Version             Repository            Size
================================================================================
Updating:
 pandorafms_console    x86_64    7.0NG.774-231121    artica_pandorafms     99 M
 pandorafms_server     x86_64    7.0NG.774-231121    artica_pandorafms     81 M
Transaction Summary
================================================================================
Upgrade  2 Packages
Total download size: 180 M
Downloading packages:
Delta RPMs disabled because /usr/bin/applydeltarpm not installed.
--------------------------------------------------------------------------------
Total                                               10 MB/s | 180 MB  00:17     
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
  Updating   : pandorafms_console-7.0NG.774-231121.x86_64                   1/4 
You can now start the Pandora FMS Websocket service by executing
   /etc/init.d/pandora_websocket_engine start
Updating the database schema.
MR: 65
66: (MR:66) 1071: Specified key was too long; max key length is 767 bytes
ALTER TABLE talert_actions ADD CONSTRAINT UNIQUE (name)
current MR: 65
Deleting old deprecated files
Done deleting deprecated files
  Updating   : pandorafms_server-7.0NG.774-231121.x86_64                    2/4 
Copying new version for tentacle_serverd service
pandora_server.service is not a native service, redirecting to /sbin/chkconfig.
Executing /sbin/chkconfig pandora_server on
Pandora FMS Server configuration is /etc/pandora/pandora_server.conf
Pandora FMS Server main directory is /usr/share/pandora_server/
The manual can be reached at: man pandora or man pandora_server
Pandora FMS Documentation is in: http://pandorafms.org
An existing version of pandora_server.conf is found.
Don't forget to start Tentacle Server daemon if you want to receive
data using tentacle
If Tentacle Server daemon was running with init.d script,
please stop it manually and start the service with systemctl
  Cleanup    : pandorafms_console-7.0NG.773.3-1.noarch                      3/4 
warning: file /var/www/html/pandora_console/pandora_websocket_engine: remove failed: No such file or directory
warning: file /var/www/html/pandora_console/operation/incidents/list_integriaims_incidents.php: remove failed: No such file or directory
warning: file /var/www/html/pandora_console/operation/incidents/integriaims_export_csv.php: remove failed: No such file or directory
warning: file /var/www/html/pandora_console/operation/incidents/incident_statistics.php: remove failed: No such file or directory
warning: file /var/www/html/pandora_console/operation/incidents/dashboard_detail_integriaims_incident.php: remove failed: No such file or directory
warning: file /var/www/html/pandora_console/operation/incidents/configure_integriaims_incident.php: remove failed: No such file or directory
warning: file /var/www/html/pandora_console/include/functions_integriaims.php: remove failed: No such file or directory
warning: file /var/www/html/pandora_console/include/functions_incidents.php: remove failed: No such file or directory
warning: file /var/www/html/pandora_console/include/ajax/integria_incidents.ajax.php: remove failed: No such file or directory
  Cleanup    : pandorafms_server-7.0NG.773.3-1.noarch                       4/4 
  Verifying  : pandorafms_server-7.0NG.774-231121.x86_64                    1/4 
  Verifying  : pandorafms_console-7.0NG.774-231121.x86_64                   2/4 
  Verifying  : pandorafms_console-7.0NG.773.3-1.noarch                      3/4 
  Verifying  : pandorafms_server-7.0NG.773.3-1.noarch                       4/4 
Updated:
  pandorafms_console.x86_64 0:7.0NG.774-231121                                  
  pandorafms_server.x86_64 0:7.0NG.774-231121                                   
Complete!

[Sergio]

Like it

Up

0

Down

Drop it

::

Hello,

The results seem to be that it has been correctly upgraded.

Do you have any errors in console? Is the server showing 774.

Kind regards,

Sergio B.

[JonRussell]

Like it

Up

0

Down

Drop it

::

I’m having trouble posting a reply. I’ll try it smaller sections.

[JonRussell]

Like it

Up

0

Down

Drop it

::

Hi,

I have some errors on some pages, but I think they were there before. 🙂

The server is showing the correct version number, but not the correct MR number and I have an alert in the console saying “Minor releases available”, hence why I tried to apply the MR SQL manually.

[JonRussell]

Like it

Up

0

Down

Drop it

::

Pandora FMS

Version v7.0NG.774 – Community

MR version MR65

BuildPC231121

[JonRussell]

Like it

Up

0

Down

Drop it

::

Should the MR SQL update the minor release number in the DB automatically, if it completes successfully? I usually update it manually after I run the MR SQL?

update tconfig set value='66' where token='MR';

[JonRussell]

Like it

Up

0

Down

Drop it

::

It wont let me post the SQL Errors … If I include the SQL the forum post button doesnt work. I’ll try taking a screen shot instead. 🙂