11 replies to this topic

[gvb]

Hello,

 

Last Friday I bumped onto the authors page and downloaded Tiny PXE Server.

 

Today I wanted to try it out after doing some tests with Serva first which is working fine but ain't free.

 

I have some questions about the app...

 

Is it normal that it doesn't save any settings?

The ini only has window positions it seems.

 

Having an http server build-in is nice but I can't force it to a non 80 port?

I already have a webserver on that box using port 80.

(ok I can place my files there but I prefer to have it in the PXEsrv folder)

 

Using DHCPproxy won't interfear with my normal DHCP settings, right?

 

What is the most optimal combination to have speedy booting of initrd or iso files?

 

I was currently using pxelinux + memdisk + http (in Serva) which is already faster than the tftp method.

Couldn't get the non-ISO initrd file to boot tho which might be even faster as it skips the memdisk cd emulation part?

 

But I read that iPXE might be even faster but the configs seems to be a lot different than most others.

 

 

[gvb]

I have the impression that the http server doesn't work at all.

[Wonko the Sane]

Have you checked the guide?

http://reboot.pro/to...e-server-guide/

http://www.mistyrebo...rver/index.html

It is possible that some answers to your questions are in there.

Example:

http://www.mistyrebo...esrv_config.htm

 

 

[web]

The following table lists all options that its possible to set in the [web] section of the Tiny PXE Server configuration file config.ini -

Entry Information\Settings port The default port used by the HTTPd daemon is port 80. This may cause conflicts if another web server is running on the network - use this setting to change the port used for HTTP connections. Syntax is "port=PORT_NUMBER"

Example config.ini entry - port=1024

Wonko

[gvb]

thanks for the hint, it seems that I need to manully put the settings in the ini file.

 

reading...

[gvb]

for some reason I'm getting errors now

 

14:05:42 DHCPd:67 started...
14:05:42 DHCPd:4011 started...
14:06:06 goUDP67:EAccessViolation,Access violation at address 004022D2 in module 'pxesrv.exe'. Write of address 0000001A
14:06:06 DHCPd:67 stopped...
 

 

nothing mentioned about the httpd being started and I don't see a usage of the port I set in the ini file either.

 

I'm using 1.0.0.19. I guess that's the latest?

Edited by gvb, 14 December 2015 - 01:10 PM.

[Wonko the Sane]

nothing mentioned about the httpd being started and I don't see a usage of the port I set in the ini file either.

 

I'm using 1.0.0.19. I guess that's the latest?

Yes it should be the last one.

Post your .ini file and possibly describe your network setup, it is possible that the port setting (or something else) creates a conflict of some kind.

 

Wonko

[gvb]

I copied the config.sample and edited it and now it behaves normal and the webserver is running aswell.

 

seem like some parsing problem somewhere.

 

back to the playground

[gvb]

I got my iso to boot now which is great!

 

I only noticed that the initial http fetch from the iso in memdisk is almost twice as slow as in serva.

 

I tried 2 versions of memdisk and the speed is the same so I don't think that's the bottleneck.

 

Is there something that can be tweaked to have it at the same speed?

[gvb]

ignore the slowdown, it was apparently traffic on the network here.

[gvb]

Mornin',

 

this morning I started my laptop again and for some reason it didn't get any PXE "tasks".

 

I had to put PXEsrv offline and back online again to make it work.

 

Does this enter in some kind of sleep mode?

[gvb]

This morning I was logging in into my backup server and it was sloooooooooooooooow.

 

Then it appeared that it was PXEsrv that had a high CPU load.

 

Hopefully a one time issue unless this is a known issue?

[gvb]

just an update

 

this high cpu issue happened again yesterday.

 

last night the pxe server didn't run as I forgot to start it again after an reboot for a backup soft update.