@ntozier @KevinTheJedi that seems to be a different user. My details are as above in the post.
cannot print ticket - v1.12.2
@macsoluk This thread is for @bvsantos. @KevinTheJedi was speaking to them.
If you are not experiencing the same things and seeing the same things as that user then perhaps you should consider following the posting guidelines and starting your own thread to get support tailored to your environment and issue.
Please read before requesting assistance
I will also say that every time I have seen people have a problem printing it has been a problem with their PHP accessing the tmp directory which @KevinTheJedi also suggested in this thread.
@KevinTheJedi @ntozier Gentlemen, my issue is indeed the same but i do seem to have permission on the tmp directory. AS included in my post i shared the images, you will notice that the directory exists as well as i have permissions to right to it. Which is now confusing me as why i cannot print. Need your expert opinion on this.
First you can start by using a vanilla install to test with. If you are not having issues with vanilla install then you know something is wrong with your current instance's code. You will then need to clear all production files and replace with fresh v1.14.1 (don't forget to save your include/ost-config.php file so you can put it back after you put the new files in place).
Cheers.
@KevinTheJedi Ok Let me try a separate vanilla install on the same server and see if it work. I will need a few days to do this. I will come back to you with the results soon. thanks,
24 days later
Hi @KevinTheJedi @ntozier . I had some problems, trying to do a fresh install as per your recommendation. We are now discussing have a new server altogether.
My questions is if we install a new server (new dedicated physical machine) Will it be possible to migrate the OStickets system without losing tickets and history ?
If yes, can you point me to an article of the correct steps before we can do this. I cannot afford to lose data.
I appreciate your help guys.
Performing a database backup isn't really an osTicket question. It would be a MySQL or MariaDB question. There are lots of resources (both on the forums and on the internet in general) on how to perform a database backup. You would want to google it for your specific Database software. Since you appear to be running Linux you can probably just use the mysqldump command to make a back up.
This command at the command line would do it for you:
mysqldump ost_database_name -uyouruser -pyourpassword --single-transaction --quick --lock-tables=false > /tmp/osticket-backup-$(date +%F).sql
You would have course have to change the following:
ost_database_name to the name of your osticket database.
yourdbuser to the username of the database user.
yourpassword to the password of the database user.
also note that it will put the back up in your /tmp directory.
You can change the path or move it some place more appropriate.
You should also make sure that you at least back up the /include/ost-config.php file which has the database server, dbname, dbuser, and dbuser pass, and salt in it.
4 days later
@ntozier I have worked with DBs a fair bit.
So are you saying that the process is to copy database and then copy all files?
I was thinking more of doing a fresh install of OS tickets and import data into it. This is so that i don't copy any inherent problems over. Plus i will have a newer version of mysql as well as php on the new server. Will that pose a problem ?
The database structure is different between versions so you would likely encounter issues trying to import a 1.12.x database into a 1.14.1 database structure. If you're good with dbs then you can get around them, but it will likely be time consuming.
You can just move the database, and install the 1.14.1 core files, copy the /include/ost-config.php file and then run the upgrader [which is what i do when i move sites / clone sites for testing]. I tell people to make sure that they back up both prior to doing things in case they need to restore for any reason.
a year later
Hi @ntozier. I have now used akeeba kickstart and Akeeba solo to migrate the OS Ticket to a new server.
Although the process seems to have worked, I cannot access the page.
I am seeing an error.: "Fatal Error: Contact system administrator."
I have checked the following.
The system is unable to connect to the database. (yes because i used kickstart and it was able to copy the database)
The system is unable to load the config info from the database.(How do i check this, the file does not seem to have any details about database credentials)
PHP short open tags are disabled. ( I have now enabled it)
Please advise.
Generally a
macsoluk "Fatal Error: Contact system administrator."
means that it could not connect to the database. Did you migrate the database over?
Did you create a db user / password, and grant it permissions to the migrated database?
Did you change the username, password, or database name? If so did ytou update your ost-config.php with the new details?
Got it. Thank you. now the system is working. I do want to upgrade to the latest version now. Since 1.2 is now the end of life. Could you please help me with the process to upgrade to the latest version?
You can view our Upgrade Guide here:
Cheers.
@KevinTheJedi. Thank you for the link it is very useful. However, I have made 2 changes to the current system to work for us. See below.
My question is will this php file be overwritten? and also, between version 1.12 and 1.15 is there a lot of difference in the code for the open.php file ???