Difference between revisions of "HOWTO: Upgrade the version of Java running on your preservation node"
Jump to navigation
Jump to search
(Created page with "To upgrade the version of Java running on your preservation node, you will need command-line access (usually through SSH) and administrator privileges (access to the `root...") |
|||
| Line 1: | Line 1: | ||
| − | To upgrade the version of Java running on your [[preservation node]], you will need command-line access (usually through SSH) and administrator privileges (access to the `root` account or to the `sudo` command-line tool) on your [[LOCKSS box]]. | + | The [https://www.lockss.org/ LOCKSS Development Team] released a new version of the [[LOCKSS daemon]] on 3 February 2021 (version 1.75.5). One of the changes to the software is that new versions of LOCKSS no longer support [https://en.wikipedia.org/wiki/Java_version_history#Java_SE_7 Java 7]. All machines getting updated versions of LOCKSS will need to have [https://en.wikipedia.org/wiki/Java_version_history#Java_SE_8 Java 8] or later installed, or else LOCKSS will not start. |
| + | |||
| + | If you run an ADPNet [[Preservation Node]], and you know you need, or might need, to upgrade the version of Java installed on your machine, here is a check-list for how to check that. | ||
| + | |||
| + | '''''Note.''' To upgrade the version of Java running on your [[preservation node]], you will need command-line access (usually through SSH) and administrator privileges (access to the `root` account or to the `sudo` command-line tool) on your [[LOCKSS box]].'' | ||
* If you don't have that, or if you don't know what it would mean to have that, reach out to the [[ADPNet TPC]] for help with this task. | * If you don't have that, or if you don't know what it would mean to have that, reach out to the [[ADPNet TPC]] for help with this task. | ||
* If you do have that, the process is described at [https://lockss.github.io/administrators/classic-lockss/upgrading-java lockss.github.io Upgrading Java]. | * If you do have that, the process is described at [https://lockss.github.io/administrators/classic-lockss/upgrading-java lockss.github.io Upgrading Java]. | ||
Revision as of 11:52, 23 February 2021
The LOCKSS Development Team released a new version of the LOCKSS daemon on 3 February 2021 (version 1.75.5). One of the changes to the software is that new versions of LOCKSS no longer support Java 7. All machines getting updated versions of LOCKSS will need to have Java 8 or later installed, or else LOCKSS will not start.
If you run an ADPNet Preservation Node, and you know you need, or might need, to upgrade the version of Java installed on your machine, here is a check-list for how to check that.
Note. To upgrade the version of Java running on your preservation node, you will need command-line access (usually through SSH) and administrator privileges (access to the `root` account or to the `sudo` command-line tool) on your LOCKSS box.
- If you don't have that, or if you don't know what it would mean to have that, reach out to the ADPNet TPC for help with this task.
- If you do have that, the process is described at lockss.github.io Upgrading Java.