Migration from CentOS v7

No I but I know it's something we need to do as well.  Please update the forum how your experience goes with this and which envrionment you chose.  I've read that Rocky is the new Centos but I haven't tried to install it or run D3 on it.

We're using 10.2, which version are you looking to install?

Tom

Tom,
We have 2 systems (Live and Development) both on CentOS 7... live is at 10.2 and dev is at 10.3.1.

I have the latitude of playing around with the development system and may just try the elevate project to migrate to RockyLinux 8.  If I do that, I will post the results. 

The reason that this route is attractive is we authenticate from OpenLDAP and also leverage a turnkey D3 system... just did not want to manually go through that hassle again.

However, I have been reliably advised that the best route is to spin up a new system altogether, install the new D3 release and do the usual restore from file-save, update the MD's and apply the required changes to the DM account (user-coldstart etc...).

Vincent

I have that compareAccounts D3 utility that you can use to compare your DM account against our unaltered DM account to help you see what you changed, like user-coldstart, PIBS, HOSTS, DEVICES, and other files. I may have already sent you that, but if not, let me know and I'll email it to you.

Brian,
I do not have the compareAccounts D3 utility.

It is a must have.

Please send it.

Vince,

Were you successul getting D3 10.2 to install in Rocky Linux? If so, which version are you running? When I run D3_setup I get an error message:
Errors during downloading metadata for repository 'd3depends'
curl error: access denied to remote resource for ftp://d3mv-repo:d3getRep0@ftp.rocketsoftware.com/Rocky/8.7/x86_64/repodata/repomd.xml

I did not continue as my previous experience with this missing d3depends is that required packages are not installed and the build will fail.

How did you get around it?

Tom

Tom, when I talked with Vincent, he had not yet decided between Rocky and Alma Linux. His plan is to install Rocky/Alma v9 and install D3/Linux 10.3.4 when it's available later this month. 10.2 will NOT install on any Linux version greater than 7.x.

Over the past 6 months, I've been moving customers from CentOS 5.11 to Rocky 8.5 (actually 8.7 after you install the updates.) The worst of it is the D3 install process. Brian Cram has a great set of instructions get around the problems with D3_setup. Reach out to him for that documentation. I have two issues with the newer version of Linux. First, disk partitioning is totally different. Gone are the good old days of /dev/sda. The newer versions of Linux use different disk designations and you just have to get used to them. The other problem is printing. None of the installed sites are having much success with Linux system printers (shared printers.) We've had to put the printing under the control of Accuterm and remove the system printers. So far, it hasn't been a problem for the end users. Other than that, the upgrades have been seamless and all our applications are running just fine. Hope this helps.

Hi Brian,

I just tried 10.3 and got the same error.  yum is looking for a Rocky 8.7 directory on your server and you don't have one.

Can you give me the list of packages that I need to install and I'll do it ahead of time so d3depends doesn't need to.

Thanks
Tom

Hi Vincent,

I used Rocky's migration script in January. The biggest hurdle I had was the shell, you have to make sure you are using bash. Other than that once the test phase passes you good to go. It works for CentOS 7, tried it on a CentOS8-stream and it failed miserably but the Rocky docs said it would so not surprised but was hoping.

Chuck

Richard,

We have been using Linux shared printers for over a decade now without any real issues.

I just want to share a recent discovery:
The standard instruction is to install the printers using CUPS (we use the CUPS web interface) and using the RAW printer driver in all instances.  This still holds true for dot-matrix printers.

We, however, just discovered that the normal drivers can be used with HP type laser & inkjet printers, and in so doing a whole new world of printer usage opened up... below is a snippet from our user-coldstart:

startshp 11,(11,21),0,s52,lp.unix,(lp.filter1s.pl kyo-laser) (s
assignfq 11,hp.lzr.unix (c
assignfq 21,hp.lzr.ux.17 (c
startshp 25,25,0,s51,lp.unix,(lpr -Ppick-tkt-otc) (s
startshp 32,32,1,s50,lp.unix,(lpr -PCups-PDF -o cpi=17) (s
startshp 40,40,0,s40,lp.unix,(lpr -PKyocera_ECOSYS_M2540dw -o cpi=17 -o media=letter -o sides=one-sided) (s
startshp 41,41,0,s41,lp.unix,(lpr -PKyocera_ECOSYS_M2540dw -o cpi=17 -o media=letter -o sides=two-sided-long-edge) (s
startshp 42,42,0,s42,lp.unix,(lpr -PKyocera_ECOSYS_M2540dw -o cpi=17 -o media=letter -o sides=two-sided-short-edge) (s
startshp 49,104,0,s49,lp.unix,(lpr -Pcash-mbj) (s
startshp 48,101,0,s48,lp.unix,(lpr -Pinv-mbj) (s
startshp 47,102,0,s47,lp.unix,(lpr -Plabel-mbj) (s
startshp 46,(106,116,126),0,s46,lp.unix,(lp.filter1s.pl ojp-9020-mbj) (s
assignfq 106,hp.dj.unix (c
assignfq 116,hp.dj.ux.17 (c
assignfq 126,hp.dj.ux.20 (c
startshp 45,105,0,s45,lp.unix,(lpr -Ppick-tkt-mbj) (s
startshp 44,(107,117,127),0,s44,lp.unix,(lp.filter2s.pl ojp-9020-mbj) (s

Take note of the definitions for printer Q's 40-42... any standard report (without any use of print @(-x) statements will be printed as per the lpr options.  If any print @(-x) statements are involved, then the appropriate device file must be created or modified and the relevant assignfq statement must also be applied to the print Q.

You may notice some "lpfilterxx" statements... those set the required lpr options in a script located in the /usr/local/bin library and did the same thing as the definitions for printQ #'s 

Hope this helps.

All,
Yesterday I decided to have a go at upgrading our dev system to RockyLinux v8.7 using the Elevate Project from AlmaLinux.  An attempt using the RockyLinux migration script failed due to a requirement of CentOS being at V8... we are at V7.

The migration was essentially successful barring the following issues:
D3 and the Rocket Licensing Manager failed to start.  D3 actually started after the binary was relinked via D3_setup but was extremely slow.
The SSSD service did not start.  I did not look any further into this as, given the above, it would be a waste of time.  Our LDAP authentication depends on this service.

In summary, I restored from backup and will be adhering to Rocket's upgrade best practices as below:
Don’t upgrade Linux 7 to Linux 8 in place with D3 installed. It will break D3.
Spin up a new RockyLinux 8 or AlmaLinux 8 system.
Reinstall and test all O/S related configuration changes (e.g., authentication, shared printers).
Install D3, restore your data and make the appropriate changes to the DM and other D3 accounts.

Vincent

Vince,

I had the same issues when I installed 10.3 in a VirtualBox instance of Rocky 8.7.  Brian gave me the list of packages that were required which I installed manually.  Then D3_setup ran but like you said, the license manager failed to start.  I found the systemctl service files were there but the startup failed.

My workaround was to create a shell script and use that instead.  Following the dependencies that I found in  the services files I created:

start-pick
#!/bin/sh 

/usr/lib/pick/updsn
/usr/lib/pick/TLLicMgr -s
/usr/bin/d3 -n pick0 -s -a x

and

stop-pick
#!/bin/sh 

/usr/lib/pick/d3shutdown pick0
/usr/lib/pick/TLLicMgr -k


if the license manager isn't running, pick is very slow to start.  Using start-pick to make sure everything is running before pick starts (which is what the systemctl scripts are supposed to do) makes all the difference.

Tom