OFORK Update
Update OFORK 12
Preparation: Make sure that OFORK version 7, version 8, version 9, version 10 or version 11 is installed.
Step 1: Stop all relevant services and the OFORK daemon
Make sure that there are no running services or cron jobs that try to access OFORK.
This depends on your service configuration. Here is an example:
root> /etc/init.d/cron stop root> /etc/init.d/postfix stop root> /etc/init.d/apache stop
Stop the OFORK cron jobs and the daemon in this order:
ofork> cd /opt/ofork/ ofork> bin/Cron.sh stop ofork> bin/ofork.Daemon.pl stop
Step 2: Back up the database and the existing OFORK installation
shell> cd /opt shell> mv ofork ofork-old
Step 3: Install OFORK using ofork-12.0.1.tar.gz
First download the source archive as .tar.gz - OFORK 12 Patch Level 1 tar.gz.
Extract the archive, for example with tar, into the /opt directory and rename the directory from ofork-12.0.1 to ofork as shown below.
shell> cd /opt shell> wget https://ftp.o-fork.de/ofork-12.0.1.tar.gz shell> tar xzf ofork-12.0.1.tar.gz shell> mv ofork-12.0.1 ofork
Step 4: Adjust Config.pm
Copy the file /opt/ofork-old/Kernel/Config.pm to /opt/ofork/Kernel/Config.pm
Step 5: Restore article data
If you configured OFORK so that article data is stored in the file system, you must restore the article folder from /opt/ofork-old/var/
or from the folder specified in the system configuration.
To do this, copy the corresponding folder into the new OFORK installation.
Step 6: File permissions
Please run the following command as the root user to set the file and directory permissions for OFORK.
The script tries to detect the correct user and group settings required for your setup.
shell> cd /opt/ofork/ shell> bin/ofork.SetPermissions.pl
cpan install Moo
cpan install Types::Standard
or
sudo apt-get install -y libtypes-path-tiny-perl
sudo apt-get install -y libmoo-perl
Step 7: Run the migration script
It is very important that you set and keep the correct time zone (OFORKTimeZone) for data storage.
Otherwise, the date and time of data added after the update, such as tickets and articles, may be stored with a different time zone.
Run the migration script as the ofork user, NOT as root:
ofork> cd /opt/ofork/ ofork> scripts/DBUpdate-to-12.pl
Step 8: Restart your services
This depends on your service configuration. Here is an example.
root> /etc/init.d/apache start root> /etc/init.d/postfix start root> /etc/init.d/cron start
After that, you should be able to open OFORK again without problems.
shell> cd /opt/ofork/Kernel/Config/Files shell> rm ZZZAAuto.pm
Step 9: Start the OFORK daemon
The OFORK daemon is responsible for handling asynchronous and recurring tasks in OFORK.
The daemon also handles all GenericAgent jobs and must be started by the ofork user.
shell> /opt/ofork/bin/ofork.Daemon.pl start
Our professional services will be happy to support you.