Is droplet web console output logged or capturable?

Hey friend,

The boot process should be accessible by typing “dmesg” via console or SSH. Over SSH you’d be able to copy the text. You could also do something like this to generate a link to view the content via browser:

dmesg | curl -F 'sprunge=<-' http://sprunge.us

That would spit out a short URL you could visit to see all of the output.

Jarland

ROM errors are typically logged to the system journal, which can be viewed using the dmesg command. To capture the ROM error messages during a reboot, you can use the following steps:

1. Open a terminal window.
2. Run the following command to start logging the system journal to a file:

dmesg -w > rom_error_log.txt

3. Reboot the system.
4. Once the system has rebooted, run the following command to stop logging the system journal:

dmesg -w -k

5. The ROM error messages will be logged to the rom_error_log.txt file.

You can then review the rom_error_log.txt file to see the ROM error messages that occurred during the reboot.

Hope that this helps!