2018-12-07 22:45:07	-->	Condor (~freenode@nixmagic.com) has joined ##proxmox
2018-12-07 22:45:07	--	Topic for ##proxmox is "Unofficial Proxmox VE Support | Wiki: http://pve.proxmox.com | YouTube: http://youtube.com/ProxmoxVE | Google+: http://goo.gl/14p2W | channel mode set to -r / 'block unregistered' - cant join after disconnect? --> '/msg nickserv register'"
2018-12-07 22:45:07	--	Topic set by sjas (~sjas@p2E5815D2.dip0.t-ipconnect.de) on Thu, 26 Jul 2018 17:46:58
2018-12-07 22:45:07	--	Channel ##proxmox: 222 nicks (1 op, 0 voices, 221 normals)
2018-12-07 22:45:07	--	PvNotice(ChanServ): Welcome to ##proxmox! Please read the channel topic.  If your IRC client is configured to autojoin #proxmox please update this to ##proxmox as the automatic divert won't stay forever.
2018-12-07 22:45:09	--	Channel created on Thu, 13 Oct 2011 14:46:41
2018-12-07 22:46:51	Condor	I've recently noticed this message (smbd.service: Supervising process 17270 which is not our child. We'll most likely not notice when it exits.) in my Samba server on both of my PVE nodes. Is this something I should be worried about, and is this a bug? None of my other hosts (Ubuntu, Arch, Raspbian) have this issue. The service starts up properly though, and shares are still accessible.
2018-12-07 22:47:40	-->	tryte (~tryte@gateway/tor-sasl/tryte) has joined ##proxmox
2018-12-07 22:50:27	Condor	I mean, I'll probably notice when the service goes down and the PVE shares aren't really *that* important so it wouldn't be much of a problem when the Samba services go down, but if systemd can't notice that the process exited, I think it wouldn't be able to restart it on its own either, would it?
2018-12-07 22:51:45	zapotah	running samba on the pve host is not exactly supported
2018-12-07 22:52:25	<--	tryte (~tryte@gateway/tor-sasl/tryte) has quit (Ping timeout: 256 seconds)
2018-12-07 22:52:27	zapotah	you can obviously use smb shares but i wouldnt be stupid enough to run a fileserver on a virtualization host
2018-12-07 22:52:47	Condor	I've read something about that yeah. I'm not using them for file servers, I'm using a dedicated container for that.
2018-12-07 22:53:00	Condor	Nonetheless, this issue seems to be one that's isolated to Proxmox.
2018-12-07 22:53:09	zapotah	good luck with it :3
2018-12-07 22:53:21	Condor	Seriously?
2018-12-07 22:54:52	zapotah	for my part anywaty
2018-12-07 22:54:55	zapotah	anyway*
2018-12-07 22:55:19	Condor	Well, I hope that the (other) maintainers are a bit *more
2018-12-07 22:55:25	zapotah	im not a maintainer :3
2018-12-07 22:55:27	Condor	Well, I hope that the (other) maintainers are a bit *more* serious about this.
2018-12-07 22:55:32	Condor	Fortunately.
2018-12-07 22:55:52	zapotah	if i was, i wouldnt really bother with something that doesnt exactly have anything to do with pve
2018-12-07 22:56:28	zapotah	your issue somehow has something to do with systemd anyway or with how smbd forks
2018-12-07 22:56:49	zapotah	id look into what that pid actually is
2018-12-07 22:57:11	Condor	Well this pretty much does. It's an issue that's recently occurred in Proxmox and doesn't seem to be present anywhere else.
2018-12-07 22:57:22	zapotah	its not an issue with any pve component
2018-12-07 22:57:30	zapotah	its an issue with a third party component
2018-12-07 22:58:06	zapotah	wether it is due to systemd shipped with pve or not
2018-12-07 22:58:09	Condor	Sure it's probably something in Samba or systemd, but that doesn't explain that the only systems that have this issue are Proxmox hosts.
2018-12-07 22:58:30	zapotah	Condor: still not relevant and im finding it hard to see why you dont understand that
2018-12-07 22:58:45	Condor	Because it's only present on Proxmox hosts!
2018-12-07 22:58:54	zapotah	._.
2018-12-07 22:59:26	zapotah	ill split this into small words
2018-12-07 22:59:29	zapotah	third.
2018-12-07 22:59:31	zapotah	party.
2018-12-07 22:59:35	Condor	How is systemd or Samba responsible when Arch, Ubuntu, Raspbian, all of them run that stack too, yet they don't have that issue?
2018-12-07 22:59:47	zapotah	because pve is responsible for pve
2018-12-07 22:59:55	zapotah	its not a general purpose distro
2018-12-07 23:00:19	Condor	And how would I explain *that* to upstream devs? When it clearly isn't an upstream issue when other downstream implementations don't have it?
2018-12-07 23:00:39	zapotah	its a virtualization platform _highly_ _specialized_ for its purpose
2018-12-07 23:00:48	zapotah	you dont run fileservers on it
2018-12-07 23:00:49	zapotah	period
2018-12-07 23:01:04	zapotah	if you do, youre literally on your own for figuring out the issue
2018-12-07 23:01:23	Condor	I know that. Does highly specialized mean that somehow one can't do their own system administration anymore outside of the fancy PVE web UI, and suddenly bugs aren't bugs anymore?
2018-12-07 23:01:46	Condor	And again, I'm not using those Samba servers as file servers.
2018-12-07 23:01:51	zapotah	pve is not a general purpose distro
2018-12-07 23:01:54	zapotah	get that through your skull
2018-12-07 23:02:17	zapotah	if youve an issue with a pve component, then its an issue
2018-12-07 23:02:20	Condor	Neither is Raspbian, it's something specialized towards the Raspberry Pi. Does that mean that oh dear I can't run Samba on it?
2018-12-07 23:02:30	Condor	Sorry, I'm done here.
2018-12-07 23:02:32	zapotah	raspbian is a general purpose distro meant to run on arm
2018-12-07 23:03:16	zapotah	it is very much different
2018-12-07 23:03:46	Condor	With that logic, Proxmox is a general purpose distro meant to run on virtualization servers.
2018-12-07 23:04:11	<--	gb00s (~gb00s@static.80.103.251.148.clients.your-server.de) has quit (Remote host closed the connection)
2018-12-07 23:04:21	zapotah	it s a virtualization platform meant to run on x86-64 arch computers
2018-12-07 23:04:40	zapotah	i have absolutely no idea how you could ever derive that conclusion of yours
2018-12-07 23:04:43	Condor	In ohter words, virtualization servers.
2018-12-07 23:04:49	zapotah	wat
2018-12-07 23:05:09	zapotah	jesus. you are thick arent you
2018-12-07 23:05:13	zapotah	good luck
2018-12-07 23:05:46	Condor	I've yet to hear of any common virtualization servers that run on other architectures. But sure I'm thick. Thanks for the good luck wishes, again, I'm done here.
2018-12-07 23:05:57	-->	tryte (~tryte@gateway/tor-sasl/tryte) has joined ##proxmox
2018-12-07 23:09:40	-->	ioscanner (~ioscanner@99.109.28.50) has joined ##proxmox
2018-12-07 23:11:04	ioscanner	Anyone play familar with moving from Hyper v to Proxmox?  I can do export-vm and get the main system up.  But it seems it has a E: drive that is not being exported.
2018-12-07 23:11:37	zapotah	ioscanner: convert the vhdx image manually?
2018-12-07 23:11:44	ioscanner	In the VM is show it as a virtual disk.  In Hyper v I only see one disk in the Virtual disks directory.
2018-12-07 23:12:31	ioscanner	I have no probem importing it using the qeum import.  Then fixing the MBR.
2018-12-07 23:12:49	ioscanner	The main disk c: comes up with no issues.
2018-12-07 23:12:59	ioscanner	But I don't see the e: disk
2018-12-07 23:13:28	zapotah	is it an actual second virtual disk or a partition?
2018-12-07 23:14:01	<--	MACscr (~MACscr@c-98-215-100-46.hsd1.il.comcast.net) has quit (Quit: Textual IRC Client: www.textualapp.com)
2018-12-07 23:15:05	xedniv	Condor, running samba in the "baremetal" side of proxmox is asking for trouble.
2018-12-07 23:15:48	xedniv	it's dumb, not necessarily meaning someone doing it is also dumb, but it increases the odds. no need for antagonizing zapotah despite his sometimes polarizing style..
2018-12-07 23:16:54	Condor	Fair enough, I'm a dumb sysadmin and an idiot that's asking for trouble by running a service on his PVE hosts. Does that make a bug any less of a bug?
2018-12-07 23:17:01	xedniv	run a container or proper guest for whatever you think you are doing. if you need to share files use nfs/iscsi.
2018-12-07 23:17:20	Condor	I am already running a container for my file server...
2018-12-07 23:17:58	xedniv	so what magic are you doing with "samba" that needs to run in the hypervisor host?
2018-12-07 23:19:14	Condor	Just seeing how much storage is still available from a Windows machine. Nothing too important and hence why I wouldn't particularly care if the process ends without systemd noticing. But nonetheless, it's an issue in PVE that I figured should be mentioned.
2018-12-07 23:19:45	zapotah	why not use a proper monitoring system for monitoring storage usage?
2018-12-07 23:19:54	Condor	Any suggestions?
2018-12-07 23:20:06	zapotah	ie. librenms
2018-12-07 23:20:17	<--	AMDler (~AMDLer@p5DED5504.dip0.t-ipconnect.de) has quit (Quit: My MacBook has gone to sleep. ZZZzzz…)
2018-12-07 23:20:35	xedniv	lol, it's not an issue in pve. but you are welcome to prove it by filing a proper bug report, another in the samba bugzilla, with enough debugging information attached to both so people can actually 'help' you. my question was also more rhetorical than anything: there is no single good reason for you to run samba in the host env
2018-12-07 23:21:07	xedniv	if you need samba for any purpose, run it in a guest or container based on whatever image works for you best.
2018-12-07 23:21:10	Condor	*facepalm*
2018-12-07 23:21:24	Condor	zapotah: thanks, I'll take a closer look at librenms
2018-12-07 23:21:50	zapotah	because setting up snmpd in the host is perfectly doable and even kinda supported
2018-12-07 23:21:54	xedniv	facepalming is what anyone reading this will do once they get to the "this dude wants to run samba in the host environment instead of a guest" part
2018-12-07 23:22:00	xedniv	zapotah, yeah
2018-12-07 23:22:10	xedniv	properly secured snmp...
2018-12-07 23:22:19	xedniv	and preferably with apparmor enforcing it
2018-12-07 23:22:27	zapotah	and you can get more data than just the storage usage from it
2018-12-07 23:22:34	<--	Condor (~freenode@nixmagic.com) has left ##proxmox ("Ciao!")