I am running 2 vm (Windows 2022 datacentre) with 1 OS drive and two drives presented as RAW disks. I created the cluster successfully without storage. When I try the enable StorageSpaceDirect
Enable-ClusterStorageSpacesDirect –CimSession
I get the following error:
This version of Storage Spaces Direct and fault domains configured as Sites do not support stretch or multisite.
Previously, I was running Windows 2019 Datacentre without any issues.
You just need to create a site. A single site with all of the node would be enough.
#Create Site Fault Domains
New-ClusterFaultDomain –Name Seattle –Type Site –Description “Primary” –Location “Seattle DC”
New-ClusterFaultDomain –Name Denver –Type Site –Description “Secondary” –Location “Denver DC”
#Set Fault Domain membership
Set-ClusterFaultDomain –Name Node1 –Parent Seattle
Set-ClusterFaultDomain –Name Node2 –Parent Seattle
Set-ClusterFaultDomain –Name Node3 –Parent Denver
Set-ClusterFaultDomain –Name Node4 –Parent Denver
Related
We have a serious BUG reported by our clients,
regarding the WPF desktop application, which is connecting to the SQL Server 2014 Express LocalDB.
At the startup of the app, the app failed connect to the local DB.
Seems that our (CNogaMedicalLocalDB)local DB instance failed to auto start.
We manually got the local DB instance's info and we saw that the instance is in the "Stopped" state.
Usually the instance is auto start and the state should be "Running"
The local DB log didn't produced any valuable data.
In case we start the local DB manually using CMD the app works fine.
The app works fine on Windows 7, 8 and 10 except the last WIN 10 build 1809 (which is our clients platform)!
The app is being used heavily by many of our other clients around the world.
We cannot reproduce the issue in our Headquarters.
We tried to reproduce the issue on our QA platforms (Virtual Machines) running WIN-10 build 1809.
Apps Technical Details:
WPF.
EF Core version 7.0.0-rc1-final
SQL Server 2014 Express LocalDB version 12.0.2000.8.
Connection string:
data source=(LocalDb)\InstanceLocalDB; Initial Catalog = MyAppDB; Integrated Security=True; MultipleActiveResultSets=True; Connection Timeout = 10
The installation package is built with Advanced Installer version 12.3.1.
5.1. The SQL Server 2014 Express LocalDB is installed together with app and contained as a prerequisite within the installation package.
5.2. The SqlLocalDB Instance creation and starting is performed also during the application's installation via a custom action (PowerShell script which is runs at the final stage of the installation processes):
SqlLocalDB.exe create "SqlLocalDBInstance"
SqlLocalDB.exe start "SqlLocalDBInstance"
Thanks in advance.
Oleg Seider
R&D Department
CNOGA Medical Ltd.
Office: +972-4-6361080 ext.127
www.cnoga.com
According to a link posted by Nickolaj Anderson (who gives credit to a David Segura for getting to the root of this issue and wrote a blog post about it), this problem is caused by Windows 10 1809 lacking two dlls: BCP47Langs.dll and BCP47mrm.dll
The following PowerShell script is posted in the link (and here, just in case the link breaks!) to enable you to update your existing boot images that have already been reloaded from Windows ADK version 1809. It is advised that you make a backup before running the script, as I'm sure you would!
Instructions as given in Nickolaj's article:
Make sure that you have access to a Windows 10 version 1809 64-bit
ISO file and extract it’s content to a location in your site server.
Create the required folders for exporting and mounting:
C:\Temp\Mount\Source
C:\Temp\Mount\Current
C:\Temp\Export
Copy the boot.wim file from the extracted location of Windows 10
version 1809 64-bit to the C:\Temp\Export folder.
Update the $BootImagePath variable in the PowerShell script with the
local path to the boot.wim / winpe.wim found in the data source of your boot image
(remember to include the file name).
Execute the script
Script:
# Variables
$SourceMountPath = "C:\Temp\Mount\Source" # Create this folder
$BootImageMountPath = "C:\Temp\Mount\Current" # Create this folder
$SourceExportFolder = "C:\Temp\Export" # Create this folder
$SourceBootPath = "C:\Temp\Export\boot.wim" # boot.wim file copied to this location from the Windows 10 1809 x64 source media
$BootImagePath = "" # Local path to your boot.wim / winpe.wim file (not boot.PACKAGEID.wim) for your boot image in ConfigMgr
# Export winpe.wim from boot.wim from Windows 10 1809 source files
$ExportImagePath = Join-Path -Path $SourceExportFolder -ChildPath "winpe.wim"
Export-WindowsImage -SourceImagePath $SourceBootPath -DestinationImagePath $ExportImagePath -SourceIndex 1
# Mount exported WinPE image
Mount-WindowsImage -ImagePath $ExportImagePath -Index 1 -Path $SourceMountPath
# Mount boot image
Mount-WindowsImage -ImagePath $BootImagePath -Index 1 -Path $BootImageMountPath
# Copy BCP47*.dll's
$SourceFilePath = Join-Path -Path $SourceMountPath -ChildPath "Windows\System32\*"
$BootImageFilePath = Join-Path -Path $BootImageMountPath -ChildPath "Windows\System32"
Copy-Item -Path $SourceFilePath -Destination $BootImageFilePath -Filter "BCP47*.dll" -Force
# Dismount exported WinPE image
Dismount-WindowsImage -Path $SourceMountPath -Discard
# Dismount boot image
Dismount-WindowsImage -Path $BootImageMountPath -Save
Hope this works for you!
Rachel
I have a node+angular app. It was working fine. I had an issue which was eaddrinuse 3000 . I run this command killall node and guess what my app which was working on x.x.x.x:8100 is not working any more.I am using bitvise by the way.
This is my directory structure. I am doing this on production server.
--app
| ---assets
---bower_components
---directives
---home
---misc
---product
---services
---user
---index.html
--backend
| ---img
---models
---node_modules
---public
---routes
---app.js
---package.json
--package.json (frontend)
So I will start off by stating I have moved the regular install location of Oracle 11.2 XE to a logical volume (/oracle) I had created on my RHEL 6.6 server. After shutting down both the database and the Oracle listener, I performed...
$ cp -R /u01/app/* /oracle
$ rm -rf /u01/app/oracl
$ ln -s /oracle/oracle /u01/app/oracle
Then restarted the listener and the database. Now when I attempt to run the following as the user 'oracle' I get a message...
$ sqlplus
Enter user-name: sys / as sysdba
Enter password: ****
Connected to idle instance.
Further, when I attempt a startup I get an error.
> startup
ORA-45301: XE Edition single instance violation error
I have attempted the solutions found here to no avail.
Here is the output for my listener controller:
bash-4.1$ lsnrctl status
LSNRCTL for Linux: Version 11.2.0.2.0 - Production on 10-MAR-2015 10:26:25
Copyright (c) 1991, 2011, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC_FOR_XE)))
STATUS of the LISTENER
------------------------
Alias LISTENER
Version TNSLSNR for Linux: Version 11.2.0.2.0 - Production
Start Date 10-MAR-2015 10:25:57
Uptime 0 days 0 hr. 0 min. 28 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Default Service XE
Listener Parameter File /u01/app/oracle/product/11.2.0/xe/network/admin/listener.ora
Listener Log File /u01/app/oracle/diag/tnslsnr/dev/listener/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC_FOR_XE)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=dev)(PORT=1521)))
Services Summary...
Service "PLSExtProc" has 1 instance(s).
Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully
I'm really quite lost as to what to attempt next. I know I could just reinstall and keep the directory in its proper location but I need it to be in it's own logical volume.
EDIT
Some further information to help clarify my system...
bash-4.1$ env | grep ORA
ORACLE_SID=XE
ORACLE_BASE=/oracle/oracle
ORACLE_HOME=/oracle/oracle/product/11.2.0/xe
bash-4.1$ env | grep TNS
TNS_ADMIN=/oracle/oracle/product/11.2.0/xe/network/admin
bash-4.1$ ps -aux | grep pmon
oracle 2431 0.0 0.2 1265956 16652 ? Ss 11:43 0:00 xe_pmon_XE
FURTHER EDIT
Attempting to sign in to sqlplus using the SYSTEM user returned an error:
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
Linux-x86_64 Error: 2: No such file or directory
FURTHER EDIT
Output of the ipcs command
bash-4.1$ ipcs
------ Shared Memory Segments --------
key shmid owner perms bytes nattch status
0xc0a59444 32768 oracle 660 4096 0
------ Semaphore Arrays --------
key semid owner perms nsems
0xd4a9963c 229378 oracle 660 104
0x884d8f34 491523 oracle 660 104
------ Message Queues --------
key msqid owner perms used-bytes messages
Check output of ipcs command and try to delete all shared memory segments/semaphores owned by Oracle.
When Oracle starts it uses two strings ORACLE_SID(uppercase) and ORACLE_HOME, hashes these two strings and uses this hash value a key for shmget call. So even if you append slash / to ORACLE_HOME everything is different from Oracle's perspective - even if the disk path is the same.
So I think you moved ORACLE_HOME into some other location, but the old value was preserved somewhere and now Oracle thinks that you are trying to start multiple instances.
EDITED: I'm not sure about XE, but regular Oracle editions are shipped as a bunch of .o object files. These files are linked during installation, but you can also re-link Oracle anytime. Check the script $ORACLE_HOME/bin/relink if the old ORACLE_HOME is hardcoded in it. And then try to re-link all libraries by executing relink all. Also note that Oracle uses link option -Wl,-rpath=..., so some Oracle binaries have library search patch compiled in them.
For Standard/Enterprise edition it is not problem to copy binaries into different Oracle home.
Check in /u01/app/oracle/product/11.2.0/xe/dbs/ if you have renamed your XE database or attempted to create a new one, you must be sure there is only one database known by xe. It's limited to one instance.
/etc/init.d/oracle-xe stop
cd /u01/app/oracle/product/11.2.0/xe/dbs/
rename any unused pwfile and spfile to .old
/etc/init.d/oracle-xe start
Issue was a wrong entry in tsnnames.ora (I had added a line that shouldn't of been there) and as well the permissions for my /oracle directory were incorrect. Thank you to everyone who tried to help, it was greatly appreciated.
I know this has been asked before but I have tried every suggestion i've found but nothing seems to work
My localhost seems to take forever to load pages (up to 30 secs). Ihave the follwoing installed on Windows 7
I am running:
Apache 2.4
PHP 5.4.9
MySQL 5.5.25
Things I have tried:
Edited the hosts file in Windows\System32\drivers\etc
# localhost name resolution is handled within DNS itself.
127.0.0.1 localhost
Edit the http.conf file to give a ServerName
# If your host doesn't have a registered DNS name, enter its IP address here.
#
ServerName 127.0.0.1:80
Has anyone got any other suggestions?
I recently did a clean install of Mountain Lion on my Mac Mini Server.
I installed version 3.0.18 using a gem according to the directions on http://www.phusionpassenger.com with no errors that I could see.
rvmsudo gem install passenger-enterprise-server-3.0.18.gem
rvmsudo passenger-install-apache2-module
Here are my entries in /etc/apache2/httpd.conf with my username masked:
LoadModule passenger_module /Users/username/.rvm/gems/ruby-1.9.3-p327/gems/passenger-enterprise-server-3.0.18/ext/apache2/mod_passenger.so
PassengerRoot /Users/username/.rvm/gems/ruby-1.9.3-p327/gems/passenger-enterprise-server-3.0.18
PassengerRuby /Users/username/.rvm/wrappers/ruby-1.9.3-p327/ruby
I uncommented out the following statement:
Include /private/etc/apache2/extra/httpd-vhosts.conf
Here is a sample virtual host entry. I have three of them in the file.
<VirtualHost *:80>
ServerName www.mydomain.com
ServerAlias mydomain.com
PassengerAppRoot /Users/username/Sites/myfolder/
DocumentRoot /Users/username/Sites/myfolder/public
<Directory /Users/username/Sites/myfolder/public>
Allow from all
AllowOverride all
Options -MultiViews
</Directory>
</VirtualHost>
I have restarted Apache several times. Here is information from my server:
[~]$ ps -ef | grep Passenger
501 18804 303 0 12:39PM ttys000 0:00.00 grep Passenger
[~]$ rvmsudo passenger-status
Password:
**ERROR: Phusion Passenger doesn't seem to be running.**
[~]$ rvmsudo passenger-config --version
3.0.18
I have tried doing online searches on this. I was surprised that there was not all that much on this specific error even though from my understanding Passenger has been around for a few years. I have posted this issue on the Phusion Passenger Google Groups but have not heard anything.
Any help would be appreciated, the sooner the better LOL. Seriously I need to have one of my three websites up by tomorrow evening. This is the only issue stopping that from happening. Thanks again.
I continued searching but still did not find anything on this error for people using Mountain Lion. After several days of utter frustration I decided to contact Phusion since I had recently purchased one of the support packages. The support I received was more than worth what I paid for it. I had come to the conclusion that something must have changed somewhere between Lion and Mountain Lion but did not know where to look.
The setup I tried after upgrading to Mountain Lion (OS X Server) worked perfectly when I used Passenger with Lion Server. After a lot of extensive checking the support person decided to try making the changes I made in /etc/apache2/httpd.conf in the config file for the Web Service located in /Library/Server/Web/Config/apache2/httpd_server_app.conf. All my Rails applications loaded perfectly. Apparently the other config file is either ignored or something. When the support person led me in trying things in /etc/apache2/httpd.conf and checking logs nothing appeared in them. This is when he decided to try updating the Web Service config file.
Note: I have to give a shout out to the support team at Phusion. When I tell you that they searched for a needle in a haystack I am not exaggerating. I created several files with notes from their support that I hope to never have to use again. They were excellent and very easy to work with.