Looking to use ConvertFrom-String on Linux as per the example from the help file:
**********************
PowerShell transcript start
Start time: 20230204142830
Username: mordor\nicholas
RunAs User: mordor\nicholas
Configuration Name:
Machine: mordor (Unix 5.15.0.58)
Host Application: /snap/powershell/229/opt/powershell/pwsh.dll
Process ID: 1193147
PSVersion: 7.3.2
PSEdition: Core
GitCommitId: 7.3.2
OS: Linux 5.15.0-58-generic #64-Ubuntu SMP Thu Jan 5 11:43:13 UTC 2023
Platform: Unix
PSCompatibleVersions: 1.0, 2.0, 3.0, 4.0, 5.0, 5.1.10032.0, 6.0.0, 6.1.0, 6.2.0, 7.0.0, 7.1.0, 7.2.0, 7.3.2
PSRemotingProtocolVersion: 2.3
SerializationVersion: 1.1.0.1
WSManStackVersion: 3.0
**********************
Transcript started, output file is /home/nicholas/powershell/PowerShell_transcript.mordor.ciSjO_A6.20230204142830.txt
PS /home/nicholas/powershell> $template = #'
{Name*:Phoebe Cat}, {phone:425-123-6789}, {age:6}
{Name*:Lucky Shot}, {phone:(206) 987-4321}, {age:12}
'#
PS /home/nicholas/powershell> $testText = #'
Phoebe Cat, 425-123-6789, 6
Lucky Shot, (206) 987-4321, 12
Elephant Wise, 425-888-7766, 87
Wild Shrimp, (111) 222-3333, 1
'#
PS /home/nicholas/powershell> $PersonalData = $testText | ConvertFrom-String -TemplateContent $template
ConvertFrom-String: The term 'ConvertFrom-String' is not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
ConvertFrom-String: The term 'ConvertFrom-String' is not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
PS /home/nicholas/powershell> $PersonalData = $testText | ConvertFrom-StringData -TemplateContent $template
PS /home/nicholas/powershell> TerminatingError(ConvertFrom-StringData): "A parameter cannot be found that matches parameter name 'TemplateContent'."
ConvertFrom-StringData: A parameter cannot be found that matches parameter name 'TemplateContent'.
ConvertFrom-StringData: A parameter cannot be found that matches parameter name 'TemplateContent'.
PS /home/nicholas/powershell> help ConvertFrom-String
PS /home/nicholas/powershell> help ConvertFrom-StringData
PS /home/nicholas/powershell> $PSVersionTable
Name Value
---- -----
PSVersion 7.3.2
PSEdition Core
GitCommitId 7.3.2
OS Linux 5.15.0-58-generic #64-Ubuntu SMP Thu Jan 5 11:43:13 UTC 2023
Platform Unix
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
WSManStackVersion 3.0
PS /home/nicholas/powershell> lsb_release -a
No LSB modules are available.
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 22.04 LTS
Release: 22.04
Codename: jammy
what throws me off here is that the help file loads fine, which would indicate that the component is installed. Perhaps that's an incorrect understanding.
ConvertFrom-String is available only in Windows PowerShell, the legacy, Windows-only edition of PowerShell - it was never ported to PowerShell (Core), the modern, cross-platform edition.
On Windows only, the cmdlet is technically still available, via the Windows PowerShell compatibility feature (which comes with its own limitations); however, for the reasons stated below, it's best to avoid this cmdlet altogether.
Note: ConvertFrom-String is not to be confused with the ConvertFrom-StringData cmdlet, which is available in PowerShell (Core) as well, on all supported platforms.
However, even in Windows PowerShell / on Windows there are good reasons to avoid use of this cmdlet:
It provides separator-based parsing as well as heuristics-based parsing based on templates containing example values.
The separator-based parsing applies automatic type conversions you cannot control, and the poorly documented template language results in behavior that is inherently hard to predict.
I have played with different versions of windows 10 inside qemu/kvm (proxmox) and all of them works fine except: "Microsoft Windows 10 Enterprise 2016 LTSB 10.0.14393 Version 1607".
I don't think that the problem is connected with proxmox itself. As I know proxmox is stable and reliable system that use qemu/kvm under the hood. So lets think more about qemu/kvm. However my proxmox versions below.
root#home:~# pveversion -v
proxmox-ve: 5.3-1 (running kernel: 4.15.18-10-pve)
pve-manager: 5.3-8 (running version: 5.3-8/2929af8e)
pve-kernel-4.15: 5.3-1
pve-kernel-4.15.18-10-pve: 4.15.18-32
corosync: 2.4.4-pve1
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.1-3
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-44
libpve-guest-common-perl: 2.0-19
libpve-http-server-perl: 2.0-11
libpve-storage-perl: 5.0-36
libqb0: 1.0.3-1~bpo9
lvm2: 2.02.168-pve6
lxc-pve: 3.1.0-2
lxcfs: 3.0.2-2
novnc-pve: 1.0.0-2
proxmox-widget-toolkit: 1.0-22
pve-cluster: 5.0-33
pve-container: 2.0-33
pve-docs: 5.3-1
pve-edk2-firmware: 1.20181023-1
pve-firewall: 3.0-17
pve-firmware: 2.0-6
pve-ha-manager: 2.0-6
pve-i18n: 1.0-9
pve-libspice-server1: 0.14.1-1
pve-qemu-kvm: 2.12.1-1
pve-xtermjs: 3.10.1-1
qemu-server: 5.0-45
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.12-pve1~bpo1
In any case I have not found any similar thread on proxmox forum. That's why I post my problem here.
This is clean original msdn iso from microsoft with confirmed hash sums(installed more then 10 times).
Steps to reproduce:
Create VM with next configuration
root#home:~# cat /etc/pve/qemu-server/102.conf
bios: ovmf
boot: dcn
bootdisk: scsi0
cores: 8
cpu: host
efidisk0: local-lvm:vm-102-disk-0,size=4M
ide2: iso-backs:iso/MS DaRT 10 Eng x86 x64.iso,media=cdrom,size=600320K
machine: q35
memory: 8192
name: win10-test
net0: virtio=C2:25:D9:DD:F2:4F,bridge=vmbr0
numa: 1
ostype: win10
scsi0: local-lvm:vm-102-disk-1,size=100G
scsi1: external:vm-102-disk-0,size=100G
scsihw: virtio-scsi-pci
smbios1: uuid=9d455cbf-1fa2-495f-928d-3935ec39c245
sockets: 1
usb0: host=1c4f:0002
usb1: host=09da:9090
vmgenid: 40cd47b6-35c4-47ab-8f9e-ed2acb618fcc
Install latest virtio drivers (scsi, netkvm, baloon, qemu-fwcfg)
Accept disk auto-partitioning (4 partitions will be created for this iso)
Wait installations end and reboot the system
Boot will stuck at proxmox logo
However, I can always boot from live cd (MS DaRT), to do that I need to manually choose harddisk from "Use a device" menu.
Once it load successfully there is a chance it will boot again an indefinite number of times. I can't figure out the reason of such behavior.
I have tried to avoid this problem by installing grub. But nothing has changed - I am still able to load system through live cd and always have a random chance to stuck at default load process.
Event Viewer errors(repeatable):
Distributed COM Event_id: 10016
Eventlog Event_id: 1101
Kernel-Power Event_id: 41
Eventlog Event_id: 6008
Kernel-Power Event_id: 13
I have an Ubuntu 16.04 droplet on DigitalOcean and I'm trying to set up remote desktop capabilities for it. I followed these instructions through Step 2. However, when I start the VNC server using the vncserver command, it goes haywire and bogs down the server until it crashes. Here are excerpts from the log file:
19/12/17 23:47:52 Xvnc version TightVNC-1.3.10
19/12/17 23:47:52 Copyright (C) 2000-2009 TightVNC Group
19/12/17 23:47:52 Copyright (C) 1999 AT&T Laboratories Cambridge
19/12/17 23:47:52 All Rights Reserved.
19/12/17 23:47:52 See http://www.tightvnc.com/ for information on TightVNC
19/12/17 23:47:52 Desktop name 'X' (thoughtful:1)
19/12/17 23:47:52 Protocol versions supported: 3.3, 3.7, 3.8, 3.7t, 3.8t
19/12/17 23:47:52 Listening for VNC connections on TCP port 5901
Font directory '/usr/share/fonts/X11/75dpi/' not found - ignoring
Font directory '/usr/share/fonts/X11/100dpi/' not found - ignoring
/home/epoirier/.vnc/xstartup: 1: /home/epoirier/.vnc/xstartup: Cannot fork
xrdb: Resource temporarily unavailable
xrdb: cannot run '/usr/bin/cpp -P -DHOST=thoughtful -DSERVERHOST=thoughtful -DSRVR_thoughtful -DDISPLAY_NUM=1 -DCLIENTHOST=thoughtful -DCLNT_thoughtful -DVERSION=11 -DREVISION=0 -DVENDOR="AT&T Laboratories Cambridge" -DVNDR_AT_T_Laboratories_Cambridge -DRELEASE=3332 -DNUM_SCREENS=1 -DEXT_XC_MISC -DEXT_SYNC -DEXT_MIT_SUNDRY_NONSTANDARD -DEXT_BIG_REQUESTS -DEXT_XTEST -DEXT_MIT_SHM -DEXT_SHAPE -DSCREEN_NUM=0 -DWIDTH=1024 -DHEIGHT=768 -DX_RESOLUTION=2951 -DY_RESOLUTION=2954 -DPLANES=24 -DBITS_PER_RGB=8 -DCLASS="TrueColor" -DCLASS_TrueColor=34 -DCOLOR -DCLASS_TrueColor_24=34 /home/epoirier/.Xresources'
/usr/bin/startxfce4: X server already running on display :1
xrdb: Resource temporarily unavailable
xrdb: cannot run '/usr/bin/cpp -P -DHOST=thoughtful -DSERVERHOST=thoughtful -DSRVR_thoughtful -DDISPLAY_NUM=1 -DCLIENTHOST=thoughtful -DCLNT_thoughtful -DVERSION=11 -DREVISION=0 -DVENDOR="AT&T Laboratories Cambridge" -DVNDR_AT_T_Laboratories_Cambridge -DRELEASE=3332 -DNUM_SCREENS=1 -DEXT_XC_MISC -DEXT_SYNC -DEXT_MIT_SUNDRY_NONSTANDARD -DEXT_BIG_REQUESTS -DEXT_XTEST -DEXT_MIT_SHM -DEXT_SHAPE -DSCREEN_NUM=0 -DWIDTH=1024 -DHEIGHT=768 -DX_RESOLUTION=2951 -DY_RESOLUTION=2954 -DPLANES=24 -DBITS_PER_RGB=8 -DCLASS="TrueColor" -DCLASS_TrueColor=34 -DCOLOR -DCLASS_TrueColor_24=34 /home/epoirier/.Xresources'
/usr/bin/startxfce4: X server already running on display :1
/etc/xdg/xfce4/xinitrc: 8: /etc/xdg/xfce4/xinitrc: Cannot fork
/etc/xdg/xfce4/xinitrc: 8: /etc/xdg/xfce4/xinitrc: Cannot fork
cpp: error: vfork: Resource temporarily unavailable
/usr/bin/startxfce4: X server already running on display :1
sh: 1: Cannot fork
This is the beginning of the log and it descends into more chaos from here with many different "Cannot fork" warnings. Nothing from the command line indicates that something is going wrong when starting the VNC server. Anyone have any ideas on what's going wrong here?
You are probably running out of file descriptors for the user running that process.
Check what is the current limit with ulimit -n and change accordingly.
Node version: 4.8.0
Platform: Linux 3.16.0-4-amd64 #1 SMP Debian 3.16.36-1+deb8u2 (2016-10-19) x86_64 GNU/Linux
Node crashed during the Garbace collection but without any other high level pattern (maybe related to https://github.com/nodejs/node/issues/3715).
Unfurtunately I don't have any code to reproduce as I was not able to isolate the problem.
This is the crash stack trace captured with segfault-handler module:
PID 24495 received SIGSEGV for address: 0x3809f3d021f8
<path_node_modules>/segfault-handler/build/Release/segfault-handler.node(+0x1a5b)[0x7f7dd565ca5b]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7f7dd9c20890]
/usr/bin/nodejs(_ZN2v88internal20MarkCompactCollector22ProcessWeakCollectionsEv+0xfd)[0xaec4dd]
/usr/bin/nodejs(_ZN2v88internal20MarkCompactCollector15MarkLiveObjectsEv+0x214)[0xaf3a14]
/usr/bin/nodejs(_ZN2v88internal20MarkCompactCollector14CollectGarbageEv+0x11)[0xaf47e1]
/usr/bin/nodejs(_ZN2v88internal4Heap11MarkCompactEv+0x60)[0xaaafe0]
/usr/bin/nodejs(_ZN2v88internal4Heap24PerformGarbageCollectionENS0_16GarbageCollectorENS_15GCCallbackFlagsE+0x4c0)[0xac2be0]
/usr/bin/nodejs(_ZN2v88internal4Heap14CollectGarbageENS0_16GarbageCollectorEPKcS4_NS_15GCCallbackFlagsE+0x238)[0xac30f8]
/usr/bin/nodejs(_ZN2v88internal4Heap15HandleGCRequestEv+0x8f)[0xac3aef]
/usr/bin/nodejs(_ZN2v88internal10StackGuard16HandleInterruptsEv+0x31c)[0xa6041c]
/usr/bin/nodejs(_ZN2v88internal18Runtime_StackGuardEiPPNS0_6ObjectEPNS0_7IsolateE+0x2b)[0xca51ab]
[0x2f2137d0963b]
And also this other stack sometimes:
PID 7545 received SIGSEGV for address: 0x68233500009
/home/documentapp/node_modules/segfault-handler/build/Release/segfault-handler.node(+0x1a5b)[0x7f89249bfa5b]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7f8928f83890]
/usr/bin/nodejs(_ZN2v88internal32IncrementalMarkingMarkingVisitor26VisitFixedArrayIncrementalEPNS0_3MapEPNS0_10HeapObjectE+0x3fe)[0xad51ee]
/usr/bin/nodejs(_ZN2v88internal18IncrementalMarking4StepElNS1_16CompletionActionENS1_18ForceMarkingActionENS1_21ForceCompletionActionE+0x30c)[0xad2a7c]
/usr/bin/nodejs(_ZN2v88internal8NewSpace15SlowAllocateRawEiNS0_19AllocationAlignmentE+0x78)[0xb00f18]
/usr/bin/nodejs(_ZN2v88internal4Heap11AllocateRawEiNS0_15AllocationSpaceES2_NS0_19AllocationAlignmentE+0x109)[0xa64719]
/usr/bin/nodejs(_ZN2v88internal4Heap20AllocateFillerObjectEibNS0_15AllocationSpaceE+0x19)[0xaabd19]
/usr/bin/nodejs(_ZN2v88internal7Factory15NewFillerObjectEibNS0_15AllocationSpaceE+0x2d)[0xa64c5d]
/usr/bin/nodejs(_ZN2v88internal29Runtime_AllocateInTargetSpaceEiPPNS0_6ObjectEPNS0_7IsolateE+0x5e)[0xca52ee]
[0x1e31ede06355]
Can someone give me some hint on how I can find the prblem? Thanks
If you prefer you can also answer on the node issues that I have created:
https://github.com/nodejs/node/issues/11606
Additional information:
Node framework: express, Sails.js
My native modules founded with find node_modules -name '*.node' are:
node_modules/bcrypt/build/Release/bcrypt_lib.node
node_modules/bcrypt/build/Release/obj.target/bcrypt_lib.node
node_modules/segfault-handler/build/Release/segfault-handler.node
node_modules/segfault-handler/build/Release/obj.target/segfault-handler.node
The problems seems to be cause by mongodb logs that fill up the disk space a some point. Was actually hard to see because we clean this periodically so was not critical at the moment I've checked.
Receiving following when trying to render using three.js.
THREE.WebGLProgram: shader error: 1282 gl.VALIDATE_STATUS false
gl.getProgramInfoLog not linked.
I have gotten my project running on a Windows 10 laptop and now trying to get it running on a Windows Server 2012. I speculate that it might be due to the server not having a real GPU, but I am no OpenGL developer and it's all chinese to me. This is what the DXDIAG says:
Display Devices
Card name: RDPUDD Chained DD
Manufacturer:
Chip type:
DAC type:
Device Type: n/a
Device Key: Enum\ROOT\BASICRENDER
Display Memory: n/a Dedicated Memory: n/a
Shared Memory: n/a
Current Mode: 1920 x 1080 (32 bit) (32Hz)
Driver Name: Driver File Version: ()
Driver Version:
DDI Version: 9Ex
Feature Levels:
Driver Model: Graphics Preemption: Compute Preemption: Driver Attributes: Final Retail Driver Date/Size: , 0 bytes
WHQL Logo'd: n/a
WHQL Date Stamp: n/a Device Identifier: {D7B71AF4-43CC-11CF-3921-F003ADC2CB35}
Vendor ID: 0x1414
Device ID: 0x008C
SubSys ID: 0x00000000
Revision ID: 0x0000 Driver Strong Name:
Rank Of Driver:
Video Accel:
DXVA2 Modes:
Deinterlace Caps: n/a
D3D9 Overlay: Not Supported
DXVA-HD: Not Supported
DDraw Status: Not Available
D3D Status: Enabled
AGP Status: Not Available
So the process is as usual to install node-gyp, which is risky business. That requires Visual C++ Build tools, which is installed on the server. Python 2.7 is installed and I've run the commands that are stated in the Installation section: https://github.com/nodejs/node-gyp
Then I use headless gl to be able to create the WebGL context in Three.js. That requires d3dcompiler_47.dll, which is added to the system32 folder. https://github.com/stackgl/headless-gl
The thing is that the server is pretty locked.. I am not able to do npm install of modules due to self signed certificate, probably since I am not allowed to do jack on the server. Now I'm pretty much stuck.. I don't know if my error is due to some compiler not being installed, if a module needs to be installed on the server, if node-gyp is mocking with me or whatever. It's a complete mess. But the server do work on my own machine. Anyone that have encountered something like it and could point me in a direction? Would be greatful!