Forum: helpMonitor Forum | Start New Thread
By: Franck Villaume on 2018-02-02 13:49
1) well done!
2) about FRS warning: it says that your database has some references but these references do not exist on the file system.
This script is generating zipfile of the latest release for each package.
Before generating the zipfile, the script checks if the main folder of the package exists.
The folder path format is:
You should check for these folders on your filesystem. If the folder exists, check about permission. The script is running as root, so it should not be a problem.
Then check in the database or through the WUI if the package has releases and optionnally has files.
If the package has releases and has files, something is missing on your filesystem. Do you copy all data from your previous system?
If the package has no release and/or no files, the warning can be skipped.
By: Andre Morrby on 2018-02-02 12:21
error.log (3) downloads
Think I managed to get the database changes done.
Got some errors/warnings from: /usr/share/fusionforge/db/20141105-frs-ziplatest.php (see attached file)
could you point me in the right direction on whats need to be fixed?
By: Franck Villaume on 2018-01-05 12:55
From my point of view, your database is missing a lot of information in database_changes. (see previous post on this topic)
My approach would be:
- check your fusionforge version you are running (in my exemple, I assume you are running 5.3.0)
- check the content of https://scm.fusionforge.org/anonscm/gitweb?p=fusionforge/fusionforge.git;a=tree;f=src/db;h=15c7609ed51da41eb863d56e8bd18171bf7efd1d;hb=91b0b0a808f0c90e60e4c496ad808610519a21ff which is the full list of script that should have be run to install or upgrade your database.
- on your new installation:
* when you hit an error, check if the ownership is ok. If ownership is not gforge, then change it to gforge and rerun the upgrade.
* when you hit another error but ownership, check the first error message. check the script accordingly to see if the script has be run against your database. You may need to execute partially some elements from the upgrade script and insert the value in database_changes table. Or if you think the upgrade script does not need to be apply on your database, then just insert the value in database_changes table.
In the current error message you are pointing:
- check the artifact_idx table.
- check the upgrade script 20120703-precompute-fti-vectors.sql
- execute the elements of this script that you think are needed
- insert the script in database_changes
Hope this help.
By: Andre Morrby on 2018-01-05 09:54
apt3.log (4) downloads
Changed the owner of artifact_idx to gforge tried to run the installer again.
Got some new errors when running the installer. I have attached a log file.
By: Franck Villaume on 2017-12-22 13:53
|yes, in your case, it should be gforge.|
By: Andre Morrby on 2017-12-22 08:00
Schema | Name | Type | Owner
public | artifact_idx | table | postgres
Do i need to change the owner to gforge?
There are a few tables with postgres as owner, the rest is gforge.
By: Franck Villaume on 2017-12-19 14:22
you are in the right track. To perform your upgrade, you may need to fix/adjust your database since (from my point of view and I may be wrong) your database is missing some elements.
Can you check if the following table exists in your database: artifact_idx?
Can you check ownership of this table?
You may have to modify ownership of this table: artifact_idx
By: Andre Morrby on 2017-12-19 08:36
apt2.log (3) downloads
I got some new error when trying to run the update again.
I did a rollback of the VM to the point before the latest update.
1. apt-get uppdate && apt-get upgrade then reboot.
2. psql> insert into database_changes (filename) VALUES ('20111017-schema-convergence-from-nondeb.sql');
3. Installed fusionforge from http://fusionforge.fusionforge.org/deb/ jessie-6.0/
I have attached the log from apt-get install fusionforge
Maybe it is easier to set up a new VM and migrate fusionforge to it?
By: Franck Villaume on 2017-12-16 08:31
thank for the information.
It seems that your database is missing one entry in database_changes. And I dont know why. Your database_changes includes older files and newer files to 20111017-schema-convergence-from-nondeb.sql
I believe the database does not need this file to be execute. Just run this sql command against your database:
psql> insert into database_changes (filename) VALUES ('20111017-schema-convergence-from-nondeb.sql');
And rerun the fusionforge upgrade.
By: Andre Morrby on 2017-12-15 15:51
database_changes.txt (4) downloads
Sorry for late reply.
I have attached the output from database_changes.
By: Franck Villaume on 2017-12-04 14:10
can you provide the full content of database_changes?
I'm surprise that you have 2012* script where 2011* needs to be execute.
By: Andre Morrby on 2017-12-04 12:53
root@test:~# lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 8.9 (jessie)
root@test:~# psql --version
psql (PostgreSQL) 9.4.15
By: Franck Villaume on 2017-11-24 15:34
thanks for the file.
What version of debian are you using? Jessie I suppose. Is it fully uptodate?
What version of postgresql?
What version of fusionforge are you using?
What is the last entry in database_changes table?
By: Andre Morrby on 2017-11-24 15:12
forum_attachment (3) downloads
|Se the attached file.|
By: Franck Villaume on 2017-11-22 19:36
|Can you provide me the description of the forum_attachment table?|
By: Franck Villaume on 2017-11-22 09:50
Got the attachment.
Looks like there are some errors with this script:
Running script: 20111017-schema-convergence-from-nondeb.sql
SQL: ALTER TABLE forum_attachment DROP CONSTRAINT "$1";
SQL> ERROR: constraint "$1" of relation "forum_attachment" does not exist
ERROR: constraint "$1" of relation "forum_attachment" does not exist
QUERY: ALTER TABLE forum_attachment DROP CONSTRAINT "$1";
Continue executing ([Y]es/[N]o)?
I need to investigate a little bit. I get back to you asap.
By: Andre Morrby on 2017-11-22 09:44
apt.log (8) downloads
Looks like you're right.
Se if it is working now.
By: Franck Villaume on 2017-11-22 09:33
|looks like there is no attachment. Am I wrong?|
By: Andre Morrby on 2017-11-22 09:04
|I have attached the full log.|
By: Franck Villaume on 2017-11-22 08:48
That is strange. It looks like the fusionforge-db-local package cannot run some upgrade scripts.
Can you provide the full log of deb installation ?
By: Andre Morrby on 2017-11-22 08:19
apt-error.log (3) downloads
Okay, when I install from deb http://fusionforge.fusionforge.org/deb/ jessie-6.0/ I get some new errors:
Errors were encountered while processing:
E: Sub-process /usr/bin/dpkg returned an error code (1)
I have include some more errors in the attached file.
Have I missed something?
By: Franck Villaume on 2017-11-15 10:54
the issue is due to PHP7.
The current fusionforge version available in Debian Official Repo is a little old.
You may want to use the autopublished packages from FusionForge DEB repo: https://fusionforge.org/plugins/mediawiki/wiki/fusionforge/index.php/DEB_Installation#Autobuilt_packages_from_the_project
By: Andre Morrby on 2017-11-14 22:07
I have taken over an VM running fusionforge and now want to upgrade it to verison 6.
The VM is running Debian 8.
I have installed fusionforge from backports: apt-get install -t jessie-backports fusionforge
When I run the post install script (/usr/share/fusionforge/bin/post-install.sh) i get the following error:
PHP Fatal error: Class 'FFError' not found in /usr/share/fusionforge/plugins/contribtracker/common/ContribTrackerPlugin.class.php on line 275
I'm new to fusionforge so I'm pretty sure i have missed something of importance.