pxe booting http retrieval failures [closed] - http

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 5 years ago.
Improve this question
I am attempting to pxe chain boot with http download. The problem I am having is the file retrieval always just stops on one of the random files below, at some random % complete. Usually it is the boot.wim, but I assume this is only because it is the largest. It has stopped on a simple font file as well though.
What could be causing this sporadic download behavior?
If I attempt a windows download off the samba share where those files are, the download is 1-2 secs. If I wget it from a nix host its about the same. Only when pxe is attempting to retrieve them does it seem to have an issue. I am fairly new to all this so hopefully I am giving good info. Samba server is running via apache.
I have tried numerous builds of kernel and boot.wim. Frankly, Im at a loss.
<%#
kind: PXELinux
name: Windows PXELinux
oses:
- Windows Server 2012
- Windows Server 2012 R2
- Windows Server 2016
%>
DEFAULT linux
LABEL linux
KERNEL ipxe.lkrn
APPEND dhcp && chain <%= foreman_url('iPXE') %>
IPAPPEND 2
the chain then goes to:
#!ipxe
kernel http://puppet.lab.beer.town:717/sources/Microsoft/Windows/6.3/../boot/wimboot gui
initrd http://puppet.lab.beer.town:717/sources/Microsoft/Windows/6.3/../boot/boot/fonts/segmono_boot.ttf segmono_boot.ttf
initrd http://puppet.lab.beer.town:717/sources/Microsoft/Windows/6.3/../boot/boot/fonts/segoe_slboot.ttf segoe_slboot.ttf
initrd http://puppet.lab.beer.town:717/sources/Microsoft/Windows/6.3/../boot/boot/fonts/segoen_slboot.ttf segoen_slboot.ttf
initrd http://puppet.lab.beer.town:717/sources/Microsoft/Windows/6.3/../boot/boot/fonts/wgl4_boot.ttf wgl4_boot.ttf
initrd http://puppet.lab.beer.town:717/sources/Microsoft/Windows/6.3/../boot/bootmgr bootmgr.exe
initrd http://puppet.lab.beer.town:717/sources/Microsoft/Windows/6.3/../boot/boot/BCD BCD
initrd http://puppet.lab.beer.town:717/sources/Microsoft/Windows/6.3/../boot/boot/boot.sdi boot.sdi
initrd http://puppet.lab.beer.town:717/sources/Microsoft/Windows/6.3/../boot/boot.wim boot.wim
imgstat
boot
Edit 1:
here is a screenshot showing the connection just freezing. all the established # 0, are the files that worked fine. the one stuck here is the boot wim (this time)

Issue here was the ipxe version on the server was like 3 years old. We git cloned it, and remade(make) the ipxe.lkrn. Files download just fine now.

Related

Ubuntu 22.04 updated failed [closed]

Closed. This question is not about programming or software development. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 days ago.
Improve this question
I ran software updater last night, and it indicated that it completed normally and asked me to reboot. I assume that is was updating the kernel from 5.15.0-58-generic to 5.15.0-60-generic. On reboot, I received a bunch of messages ending with "kernel panic: No working init found." Using the advanced boot options, I found that .58 version was available. It indicated major disk problems and said to run fsck, which I did. I pressed "y" about a hundred times, and then .58 booted normally while .60 still produces a kernel panic. I then saved all my personal files. Right now, .58 seems to be running normally, and Software Updater runs with no problems.
I want to avoid reloading the OS, as I have custom WiFi and printer software that requires extra effort, as well as Virtual Box. And yes, the have been running happily through many updates. What are my options?

How to make sure that a process on Gunicorn3 runs continuously? [closed]

Closed. This question is not about programming or software development. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 3 months ago.
Improve this question
I have a flask app deployed on a Ubuntu server. I use Nginx, and Gunicorn3. I know from this StackOverflow post that one of the correct ways to have the app running continuously on the server is to use something like:
gunicorn3 app:application --workers 3 --bind=127.0.0.1:1001 --daemon
But to be completely safe, since there are many other processes running on that server, I would like to find a way to check whether this process IS indeed running, and if it is NOT running (for whatever reasons) then to start it again.
In addition to that question, to make the app working at reboot, I use the following cronjob:
#reboot bash ~/restart_processes.sh
Where the .sh file executes the command line given above for starting Gunicorn3. Is this good practice or is there a better way to achieve the same result?
Thank you!
Kind regards,
I always use to deploy it in production with supervisorctl + nginx. Check this tutorial . You can simply start, restart or stop with a command.

Google Cloud VM Instance with Wordpress Repeatedly Crashes [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 3 years ago.
Improve this question
I've got a newly deployed Google Cloud f1-micro VM Instance using the Google Click to Deploy Wordpress solution. I've done some basic configurations such as a static IP, DNS config, persistent disk, etc. I also imported data from a previous Wordpress install.
The issue is that about every 10-15 minutes the server crashes and becomes unresponsive. Error 500 when trying to view any page, and SSH becomes unreachable. The console shows the VM Instance is still running though. I have to Reset the VM Instance, and then everything is restored within a few seconds. CPU usage is almost always below 50%. The site currently has almost zero traffic, just me testing it.
Any idea what may be causing it to freeze/crash so often? I know the f1-micro is not a powerful server, but I've read a lot about running Wordpress on it and it seems like it should be able to handle a low traffic website.
You can see system log from console in Web UI
Or you can use CLI
gcloud compute --project={your project id} instances get-serial-port-output {vm name}
f1-micro only have 0.2core and 0.60 memory. it can not support both wordpress and mysql. I think it out of memory, and system keep kill your process (mysql or wordpress). I suggestion you upgrade to bigger vm.

AWS EC2 Rstudio Server Error Occured During Transmission [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Closed 7 years ago.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Improve this question
After over a month, I have managed to piece together how to setup an AWS EC2 server. It has been very hard to upload files as there are very conservative (size) limits when done via the upload button in Rstudio Server. The error message when this is attempted is "Unexpected empty response from server".
I am not unique in this respect e.g. Trouble Uploading Large Files to RStudio using Louis Aslett's AMI on EC2
I have managed to use the following commands through putty and this has allowed me to upload files via either filezilla or winscp.
sudo chown -R ubuntu /home/rstudio
sudo chmod -R 755 /home/rstudio
Once I use these commands and log out, I can no longer access rstudio on the instances in future logins. I can relogin to my instances via my browser, but I get the error message:
Error Occurred During Transmission
Everything is fine other than once I use Putty I lose browser access to my instances.
I think this is because the command is change of ownership or similar. Should I be using a different command?
If I don't use a command I cannot connect between filezilla/winscp and the instance.
If anyone is thinking of posting a comment that this should be closed as it is a hardware issue, I don't have a problem with hardware. I am interested in the correct coded commands.
Thank you :)
Ok so eventually I realised what was going on here. The default home directory size for AWS is less than 8-10GB regardless of the size of your instance. As this as trying to upload to home then there was not enough room. An experienced linux user would not have fallen into this trap, but hopefully any other windows users new to this who come across this problem will see this. If you upload into a different drive on the instance then this can be solved. As the Louis Aslett Rstudio AMI is based in this 8-10GB space then you will have to set your working directory outside this, the home directory. Not intuitively apparent from Rstudio server interface. Whilst this is an advanced forum and this is a rookie error I am hoping no one deletes this question as I spent months on this and I think someone else will too.
Don't change the rights of /home/rstudio unless you know what you are doing, this may cause unexpected issues (and it actually does cause issues in your case). Instead, copy the files with filezilla or winscp to a temporary file (let say /tmp), then ssh to your instance with putty and move the file to the rstudio directory with sudo (e.g sudo mv /tmp/myfile /home/rstudio).

Debian Wheezy Networking Spontaneously Shuts Down [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
I have just recently upgraded to Wheezy. Since I have updated my server will spontaneously kill networking. What logs could I look in to see if I can find the issue? I have looked in /var/log and there are no logs that look relevant that have been updated in the past few days. This server runs headless so re-enabling networking means turning the server off and on again as I can't ssh to it.
Any suggestions would be welcome.
Thanks
var/log/syslog should have something. You can run dmesg which may pick it up if it's a kernel module problem or something - to find the module name use lspci -v | grep -i ethernet and look for the module name a few lines later (it could be e1000 or something). Use the module name when grepping the dmesg output.

Resources