What new feature of FreeBSD 10.2 is required by Rocket?
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Feb 13 2016
FreeBSD 10.3 is coming, to deploy STABLE is under consideration, and so this is probably premature to open a task for this.
Feb 12 2016
Relaunched Xessife.
Okay network modified to use Ysul public IPs, not private IP.
In T722#7167, @dereckson wrote:Ysul
According this pfSense forum thread, there wouldn't be any hotplug detection of network card in FreeBSD.
So that will wait next reboot. It's expected to be available as em1.
Decreased priority as a reboot is needed.
Created a new network IntraStorm.
Assigned to Kalix so they can provide its vision of how the channel should work.
Could be related to Capsicum — https://lists.cam.ac.uk/pipermail/cl-capsicum-discuss/2014-December/msg00004.html
Decreased priority as the task description now contains the information we need.
All seems operational.
Operations log
Firewall configuration
restrict default kod nomodify notrap nopeer restrict 127.0.0.1 server 0.fr.pool.ntp.org server 2.fr.pool.ntp.org server 3.fr.pool.ntp.org driftfile /etc/ntp.drift
Feb 11 2016
We can reach Ysul again.
In T716#7055, @dereckson wrote:Restart the management agents on the hypervisor isn't helpful:
~ # /etc/init.d/hostd restart watchdog-hostd: Terminating watchdog process with PID 94900058 hostd stopped. Ramdisk 'hostd' with estimated size of 129MB already exists hostd started. ~ # /etc/init.d/vpxa restart watchdog-vpxa: Terminating watchdog process with PID 94900730 vpxa stopped.
ETA for next update: 21:35 UTC
I'm attaching a console in a few minutes to see what happens exactly, and why it doesn't respond on the network.
We've got a ping soon after the reboot, nothing now.
Ysul restart
Hypervisor works again
[Moved to T717]
There is an issue with the hypervisor
I'm restarting Ysul, as I can't reach it through Dwellers either.
Ports assign
DNS configuration