October 15, 2021
unable to import scheduled tasks through .car file – CF 2021
Comments
(6)
October 15, 2021
unable to import scheduled tasks through .car file – CF 2021
Newbie 1 posts
Followers: 1 people
(6)

Hi – I’ve installed CF 2021 on a server and I have a .car file that includes all my scheduled tasks (I can see them listed when I click “deploy”), but after it says it has successfully deployed my archive file, the scheduled tasks aren’t there (the datasources and server settings and all that imported just fine). Anyone encountered this and have any idea? (This issue also ends up breaking my install of CF 2021 – after this import, if I try to restart the application server, it no longer runs and I end up having to uninstall and reinstall CF 2021.)

Thanks.

6 Comments
2022-05-02 14:35:30
2022-05-02 14:35:30

I have same issue although, I took only scheduled tasks in my car file

Like
(4)
>
Pierre23682963n3yh
's comment
2022-05-02 15:15:35
2022-05-02 15:15:35
>
Pierre23682963n3yh
's comment

Pierre, which “same issue”? If you mean that you find that CF won’t start after you attempt to import tasks, then I would point you to my comment to David back in Oct. He never replied, so it’s unclear if it helped him. But from my experience it should have.

If instead you mean that the tasks don’t import, then I would point you (and David and anyone experiencing anything that fails to import) to the CF logs, for the instance to which tried to do the import. Let’s say that is your cf2021 and its cfusion instance: then look in coldfusion2021/cfusion/logs.

In there will be at least two logs related to CAR migration, whose names start  with car. Look at those, for the time at which you did (or do) the car import. What does it show? Based on the error, we may be able to guide you to a solution.

Like
>
Charlie Arehart
's comment
2022-05-02 15:34:41
2022-05-02 15:34:41
>
Charlie Arehart
's comment

Actually the tasks didn’t import, so I have looked into coldfusion2021/cfusion/logs but I didn’t find any CAR* log files…

Then I have tried to re-run migration wizard just importing my neo-*.xml files and it did something, but it was not fully successfull because of this error :

Error”,”http-nio-8500-exec-5″,”05/02/22″,”17:12:50″,”CFADMIN”,”Could not import your ColdFusion Scheduled Tasks. – There was an error with encryption.”

What does it mean ?

Thank you for your help Charlie.

Like
>
Pierre23682963n3yh
's comment
2022-05-02 16:09:38
2022-05-02 16:09:38
>
Pierre23682963n3yh
's comment

Pierre, if you mean first that you are doing the CAR import in the CF Admin of CF2021, then yes there should definitely be CAR logs in the CF logs folder of the instance you’re using. As for whether it’s the cfusion, that depends on whether you may be using an instance OTHER than that. Look at your CF Admin. In the top right corner, it will tell you the instance name (under the “logout” button for the CF Admin).

If you ARE using the cfusion instance and its admin, but you see no car*.log files, look then at any and all other log files there which are modified at the same time as your attempt to do the car import. There should be errors in some log.

Finally, as for your attempt to instead do the first-launch migration (totally unrelated to the CAR migration), did you find some docs on that process, and how to create the cfXsettings folder (x being the old CF version) and copy in the neo*.xml files (then edit the adminconfig.xml file), etc?

And if so, did you check the logs after that? There would be migration*.log files (and beyond that, still other CF logs). Do they report any error?

Did you perhaps bring bring ONLY the neo*.xml files? Note that if the tasks had passwords set (such as for the URL being called in the task, to perform basic authentication), then the migration would fail because the new CF instance could not decrypt the passwords that had been stored by the old CF instance (in your neo-cron.xml file). You need to put also the seed.properties file (from the old CF instance) into that cfXsettings folder (holding the old version’s neo*.xml files).  That allows the migration process to decrypt those passwords (and the new CF version would encyrpt them using ITS own seed.properties.)

BTW, the CAR mechanism takes care of all that for us (the car file is a zip which you will see hold BOTH the neo*xml files and the seed.properties file, and more).

Let us know how you get on now.

Like
>
Charlie Arehart
's comment
2022-05-03 08:45:11
2022-05-03 08:45:11
>
Charlie Arehart
's comment

Charlie, I have tried CAR import again and I got files inside logs directory. My issue is related to scheduled tasks import? Here is the error from the log file :

“Error”,”http-nio-8500-exec-5″,”05/03/22″,”10:27:00″,,”Error occurred while updating scheduled tasks:”
“Error”,”http-nio-8500-exec-5″,”05/03/22″,”10:27:00″,,”class coldfusion.scheduling.ScheduleTagData cannot be cast to class coldfusion.osgi.to.ScheduleTagTO (coldfusion.scheduling.ScheduleTagData is in unnamed module of loader org.apache.felix.framework.BundleWiringImpl$BundleClassLoader @6fa5189b; coldfusion.osgi.to.ScheduleTagTO is in unnamed module of loader coldfusion.bootstrap.BootstrapClassLoader @1a565af)”

 

Then I have used the migration wizzard after including also the seed.properties file as you have adviced. This has worked properly and my scheduled tasks properly imported !

Many thanks for your support.

 

Like
2021-10-21 02:47:30
2021-10-21 02:47:30

David, I’m sure this has been very frustrating for you. But it should be solvable, and perhaps easily.

First, to be clear, the failure of the sched tasks to appear would NOT prevent CF starting. I’ve never seen that, in all the years since the CAR feature was added. Second, you should NOT need to uninstall CF to get it working. I help people find and fix such problems daily, and have never needed to reinstall it to get it working.

My bet instead would be that your CAR export included JVM settings, which upon import were implemented—but which then didn’t show their impact until a CF restart.

If you may “try it again”, copy off CF’s jvm.config file first, then do the import. Then try the restart, and when it fails to start, copy off that CHANGED version of the file, then rename the first copy and start CF. If it works, that confirms what I suspect. Then you could compare the two files to see what’s amiss.

A common problem is that the other machine (from which you EXPORTed the CAR) had CF pointing to a JVM location other than CF’s default…but the location pointed to does NOT exist on the NEW machine.

I will say also that if this is NOT it, I am willing to help you in an online consulting session, and if I can’t solve the problem, you won’t pay for the time. I doubt we’d even need an hour, and we may need as little as 15 mins (carehart.org/consulting).

Looking forward to hearing what you may find.

Like
Add Comment