Are you the publisher? Claim or contact us about this channel


Embed this content in your HTML

Search

Report adult content:

click to rate:

Account: (login)

More Channels


Channel Catalog


Channel Description:

Most recent forum messages

older | 1 | .... | 5700 | 5701 | (Page 5702) | 5703 | 5704 | .... | 6576 | newer

    0 0

    Hello

     

    I have the same problem

    Cannot connect to the depot. Verify network connections and try again.

    in logs: ERROR    depot_manager.vapi.depot_wrapper Remote depot authentication request to https://depot.vmware.com/PROD/ failed with Remote depot HTTP Request Failed (0)


    VSM 1.5

    login kotobanvv@rzds.ru

    system: Win Server 2008R2, browser chrome, proxy setting i has check twice


    0 0

    Ну, почему же "крик души"? Просто настроение хорошее

     

    Проблема-то чуть в другом: мы же не просто от нечего делать с Windows -> Linux переходим, а потому, что Windows в принципе не позволяет делать некоторые вещи (ключевые слова DPDK & SPDK), поэтому CentOS-based Linux в нашем случае уж сильно больше based, чем CentOS Там драйвера NVMe & сетевых карт не совсе стандартные будут, так сказать... Поэтому просто взять StarWind /Linux и поставит поверх готового работающего сервера и дистрибутива просто не получится: нужно будет долго его "допиливать", за что вы нас по итогу же и проклянете То есть тот сценарий, который вы описываете внизу, мы даже не думали делать Но! Мысль-то на самом деле здравая, поэтому я ее на досуге подумаю! Мы мне другую вещь скажите - если вам в таком вот режиме производительность будет +- "фиолетова" (в разумных пределах, до 50К IOPS на ноду), будет вам проще VM-based разваривать, или KVM это все-таки слишком сложно будет?

     

    Спасибо еще раз!

     

    Антон

     

    --

     

    Хм-ммм... прямо "крик - души!" какой-то.

    Ну не выглядит Ваш ответ "эмоционально нейтральным", уж простите.

     

    Да, с "зоопарком конфигураций" Вы правы.

    Другое дело, как мне кажется, что достаточно остановиться на "шапке" (раз уж у вас для VSA новой платформой ЦентОсь будет). Ну, возможно, "добить в обойму" Дебиан. Суси и прочие уже будут избыточны в вашем портфеле, как по мне.

     

    Кстати, в чём-то ваш новый VSA будет так или иначе конкурировать с Вариным VSAN и/или со ScaleIO с нутаниксом. Понятно, что рекомые плавают в новомодном болотце SDS, но когда не нужен весь функционал, то пуркуа бы и не па?

     

    Насчёт конкуренции на "физике", как я это вижу...

    Линуховая версия Старвинда "для физики" вряд ли будет конкурировать с Ceph и его аналогами - это "другая лига" (не лучше-хуже-круче-толще - просто другая).

    А вот как конкурент/замена разным Nas4free, "замёрзшим" FreeNas с OpenFiler, невнятным Nexenta`м и Open-E - почему нет?

    Простая (недорогая? фришная?) "искаропковая" одноголовая конфигурация - и более навёрнутая двух-трёхголовая "кластерная" конкуренция всяким там DRBD и прочим MelioFS`ам.

    Я б давно купил бы себе в лавку Старвинд в той же HA-конфигурации, не будь он виндовым (не, я не винхейтер и не только в доплицензии на хостовую винду дело - просто я не люблю винстораджи).

     

    Я вот, несмотря на умение поднять тот же блочный таргет на той же ЦентОси (ну или на дефолтных виндовых решениях, если угодно), тем не менее не списываю в утиль и пресловутый OpenFiler - просто потому, что возможность "не думая" быстро, буквально за четверть часа развернуть и воткнуть в инфру готовое работающее хранилище иногда бывает ценнее наличия продвинутых-прошаренных продуктов, требующих если и не вникания, то всё равно возни по их старту и настройке.

     

    И Антон, когда/если начнёте "громить" мои аргументы своими, делайте, пожалуйста, скидку на то, что я конечник, эксплуататор, ваших девелоперско-продавальных резонов разумею, конечно, но из моего окопа видно так, как это вышеописано мною.

     

    Благодарю заранее и спасибо за ответы.


    0 0

    I just realized that we connected our vROps 6 instance to vCenter on Tuesday, a day before we started having problems...seems like more than a coincidence.

     

    You mentioned that you are running vROps as well, right?


    0 0

    I went to reboot a Windows VM today, and it just hung on boot.  Eventually, I was able to find that it was the fact that the VM in question had an RDM disk attached, and the iSCSI LUN was not showing as connected, for some reason.  All I did was a rescan, and it came back, and the VM was able to boot just fine.

     

    My main question is this - why would no alert or warning show anywhere when this issue arises?  Is there any way I can make that happen?

     

    A secondary question is how would I go about determining why this happened in the first place?  The device wasn't down, nor has it been according to the device logs.  And if the system lost contact with it for some reason, why wouldn't it automatically reconnect?  Why did I have to manually rescan?

     

    Appreciate any thoughts/insights anyone may have.  I really need to get this RDM thing working, but this issue makes me nervous about it.


    0 0
  • 12/08/16--09:43: how VR keep instance per day
  • Dear All

    Hi

    my RPO is 15min

    i have a question about point in time instance

    i understand this from point in time  (instance that when i set keep 3 instance per day for the last 7 days )

    it can just save 3 snapshot every day is that means if i start first synch on 07:00 the next sync is on 07:15 and finally is on 07:30 ?

     

    or

     

    1-do it  synch continuesly every 15 min from 07:00 untill 00:00 finally just keep 3 last snapshots ?

    2 - is that mean when do 4th synch this snapshot will replaced with first snapshot ?

     

    BR


    0 0

    I seem to have fixed my issue by simply typing in a System name in the dialogue pictured below, instead of leaving it blank, which relied on the DHCP reservation/DNS entry in my router that worked under 6.0U2.

     

    I've now survived 5 ESXi reboots, using ESXi host reboot, which was set to shut down all VMs gracefully, and to restart VCSA automatically.

     

    I will continue to test and reboot, but first, a flight to catch, with my server onboard, of course ;-)

     

    Here's how I was doing 6.0U2 or 6.5 installs, choosing DHCP, and leaving System name blank (but setting up a DHCP reservation for the VM's MAC address, and setting up a DNS name, by suspending the VCSA 6.5 appliance moments after the power up button appears, and grabbing the fresh  VM's MAC, then resuming)

    2016-12-08_12-37-19.png

     

     

    I don't use DDNS:

    2016-12-08_12-37-50.png

     

     

    but figured I'd try to put in a System name anyway:

    2016-12-08_2-53-58.png

     

    Five reboots later, I seem to be good, used to fail on first or second reboot/restart of VCSA.


    0 0

    I experienced the exact same error performing a "Scan" in Update Manager after an upgrade from 6.0U2 to 6.5.  This happened on all (3) of my vCenter servers.  All (3) were running the Windows version of vCenter and Update Manager on the same box.  In all (3) cases, the error in the Update Manager log file is essentially the same as yours, except the missing file is named differently in each case.  I suspect the number after the "metadata" is a random number, which is why our results are slightly different.  It's interesting to note that the first two vCenters classify the updates as "Unknown" while the third is from Nimble.  This suggests that perhaps all of them are third-party.  I do remember loading the Nimble Connect Manager (NCM) extension into the 3rd vCenter Update Manager patch repository.  Perhaps the Update Manager migration routine from v6.0 to v6.5 isn't smart enough to migrate 3rd party extensions entirely.  It appears as though it migrates the high-level metadata, but not any of the actual files/content/zips.  In all (3) cases, the files are in fact missing from the /storage/updatemgr/patch-store/hostupdate path.

     

    In any case, I'd like to know if there is simply a way to "clear" the Update Manager repository to factory defaults.  In Windows, I would simply perform an uninstall and reinstall of Update Manager whenever I needed to reset the patch repository.  How is this done on the VCSA 6.5?

     

    Below are my log file snippets, from each vCenter:

     

    vCenter #1:

     

    [2016-12-08 11:27:30:663 'HostUpdateDepotManager' 140700199155456 ERROR]  [patchDepotManager, 221] Failed to get filesize for: /storage/updatemgr/patch-store/hostupdate/Unknown/metadata_1471377724.zip, please check if the file exists and accessible. Error: boost::filesystem::file_size: No such file or directory: "/storage/updatemgr/patch-store/hostupdate/Unknown/metadata_1471377724.zip"

     

    [2016-12-08 11:27:30:676 'SingleHostScanTask.SingleHostScanTask{58}' 140700199155456 ERROR]  [vciTaskBase, 565] Task execution has failed: boost::filesystem::file_size: No such file or directory: "/storage/updatemgr/patch-store/hostupdate/Unknown/metadata_1471377724.zip"


    vCenter #2:

     

    [2016-12-08 11:27:57:275 'HostUpdateDepotManager' 139930102200064 ERROR]  [patchDepotManager, 221] Failed to get filesize for: /storage/updatemgr/patch-store/hostupdate/Unknown/metadata_1471377323.zip, please check if the file exists and accessible. Error: boost::filesystem::file_size: No such file or directory: "/storage/updatemgr/patch-store/hostupdate/Unknown/metadata_1471377323.zip"

     

    [2016-12-08 11:27:57:281 'SingleHostScanTask.SingleHostScanTask{65}' 139930102200064 ERROR]  [vciTaskBase, 565] Task execution has failed: boost::filesystem::file_size: No such file or directory: "/storage/updatemgr/patch-store/hostupdate/Unknown/metadata_1471377323.zip"


    vCenter #3:

     

    [2016-12-08 11:28:10:166 'HostUpdateDepotManager' 140109239031552 ERROR]  [patchDepotManager, 221] Failed to get filesize for: /storage/updatemgr/patch-store/hostupdate/Nimble/metadata_1471376533.zip, please check if the file exists and accessible. Error: boost::filesystem::file_size: No such file or directory: "/storage/updatemgr/patch-store/hostupdate/Nimble/metadata_1471376533.zip"

     

    [2016-12-08 11:28:10:172 'SingleHostScanTask.SingleHostScanTask{76}' 140109239031552 ERROR]  [vciTaskBase, 565] Task execution has failed: boost::filesystem::file_size: No such file or directory: "/storage/updatemgr/patch-store/hostupdate/Nimble/metadata_1471376533.zip"


    0 0

    Yes, we've been running vRops for quite a while.  We just upgraded to v6.4 to be compliant with vCenter 6.5.  I'll report back if the OutOfMemory errors return.


    0 0

    Is there a tool or a process to convert a windows based vcenter 6 server to an appliance?  Have found the 5.5 to 6 converter but nothing for 6.0


    0 0

    Did you try casting to the required type?
    Does the Verbose switch shed some more light on the issue?
    Worst case, you'll have to go to the vSphere API.


    0 0

    So we ended up downgrading to a lower version to fix this for now.  It's been working great for us until we upgrade to 6.0 in the near future.


    0 0

    Here are a couple of examples:


    - If you are retaining 24 in a 1 day period, it will have 24 “slots” for retention in that day.  It will keep the most up to date instance for each 1 hour slot.  If you have a 15 minute RPO you will have 96 slots, but it will keep only 24 of them.  So it will retain the most up to date replica *roughly* every 4 replicas.

    - If you have say a retention of 6 in a 1 day period, then you have 4 “slots” per day.  It will retain the most up to date replica every 6 hours.  If you have a 15 minute RPO it will retain roughly every 24th replica.

     

    The oldest snapshot will be discarded to retain the newest and stay under the 24 snapshot limit.


    0 0

    Hi Oleg,

     

    many thanks for the hint with the custom group, seems to work.

     

    Regarding the Adapter issue:

    Already did the setup on client side again...successfully as it seems, also in the agent.log I see no issues but a lot of "successfully sent to server" stuff...but on the server I just see...nothing at all, also after restarting.

     

    EDIT: I just realized that it may be a licensing issue? I got the vROPS license as part of a vCenter Enterprise Plus bundle...does that include Windows endpoint agent monitoring...?


    0 0
  • 12/08/16--10:43: Re: IBM DB2 App stack
  • Is it IBM DB2 client or server application?


    0 0

    May be you need to check for any dependency for the DLLs  using dependency walker. However, I don't understand the need of adding additional Win 7 dlls into %SystemSystem% folder when the package works without them on Win 7.


    0 0

    I'm having a look at this again this evening. Somebody mentioned pass-through audio above and I can confirm that this does indeed work fine. Let me just reboot with USB 2 configuration.

     

    Cheers, Rob.


    0 0

    Well go to the foot of our stairs! That worked. You can even switch to USB 2 back from USB 3 in a live VM. I had a few quirks to begin with, i.e. no distortion and then distortion back - but twigged that having this sequence didn't work:

     

    1. USB 3 guest with headset connected to guest
    2. Shutdown and change to USB 2
    3. Power back up - no difference
    4. However, disconnect and reconnect the headset and perfect

     

    Subsequent shut down and power up - perfect.

     

    I'm pretty sure I tried this one before! I'm going to guess that USB 3 is stressing things out due to it's high transfer rates?

     

    Cheers, Rob.


    0 0

    I was able to install 4.2 in 16.04, with some minor tweaks to get things working.

    1. Download from https://my.vmware.com/group/vmware/details?downloadGroup=CART16Q3_LIN64_420&productId=578&rPId=12830
    2. In Terminal, cd to download location and run "chmod +x VMware-Horizon-Client-(version release you downloaded).bundle"
    3. In Terminal run "sudo ./VMwware-Horizon-Client-(version release you downloaded).bundle" to start the install:

    (This is the output from my install, yours may vary depending on what you've previously installed)

    Installing VMware Horizon Client 4.2.0

        Configuring...

    [######################################################################] 100%

    Installation was successful.

    Register and start installed services(s) after installation(Select

    yes, the Installer will create necessary entries in your system

    autostart or generate a launching script, so that the installed

    service(s) can be ready before the Horizon Client starts)[yes/no]: yes

     

    Do you want to check your system compatibilities for Horizon Client,

    this Scan will NOT collect any of your data?[yes/no]: yes

     

    Scanning     libxml2.so.2

        Please wait

    [######################################################################] 100%

    VMware Horizon Smart Card

        Success

    VMware Horizon Real-Time Audio-Video

        Failed        libudev.so.0

    VMware Horizon Client Drive Redirection

        Success

    VMware Horizon Multimedia Redirection (MMR)

        Failed        libgstapp-0.10.so.0

        Failed        libgstbase-0.10.so.0

        Failed        libgstreamer-0.10.so.0

    VMware Horizon PCoIP

        Failed        libffi.so.5

    VMware Horizon USB Redirection

        Failed        libudev.so.0

    VMware Horizon Virtual Printing

        Success

    VMware Horizon Client

        Failed        libudev.so.0

    1. Basic install is complete, however, as the "Failed" messages indicate, a few pieces are missing.
    2. Using "ldd" will get you a list of what is required, and where it is located, and what is missing by displaying "not found":

    $ ldd /usr/lib/vmware/view/bin/vmware-view

        linux-vdso.so.1 =>  (0x00007ffdf7510000)

        libatk-1.0.so.0 => /usr/lib/x86_64-linux-gnu/libatk-1.0.so.0 (0x00007fa1de433000)

        libgdk_pixbuf-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0 (0x00007fa1de211000)

        libgtk-x11-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 (0x00007fa1ddbc5000)

        libgdk-x11-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 (0x00007fa1dd910000)

        libgio-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 (0x00007fa1dd588000)

        libgthread-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgthread-2.0.so.0 (0x00007fa1dd385000)

        libpixman-1.so.0 => /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 (0x00007fa1dd0dd000)

        libpng12.so.0 => /lib/x86_64-linux-gnu/libpng12.so.0 (0x00007fa1dceb8000)

        libXss.so.1 => /usr/lib/x86_64-linux-gnu/libXss.so.1 (0x00007fa1dccb3000)

        libudev.so.0 => not found

        libglib-2.0.so.0 => /lib/x86_64-linux-gnu/libglib-2.0.so.0 (0x00007fa1dc9a2000)

        libgobject-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 (0x00007fa1dc74e000)

        libgmodule-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0 (0x00007fa1dc54a000)

        libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6 (0x00007fa1dc210000)

        libXinerama.so.1 => /usr/lib/x86_64-linux-gnu/libXinerama.so.1 (0x00007fa1dc00c000)

        libssl.so.1.0.2 => not found

        libcrypto.so.1.0.2 => not found

        libxml2.so.2 => /usr/lib/x86_64-linux-gnu/libxml2.so.2 (0x00007fa1dbc51000)

        libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007fa1dba37000)

        libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007fa1db6b5000)

        libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fa1db3ab000)

        libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007fa1db195000)

        libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fa1daf78000)

        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fa1dabae000)

        libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fa1da9aa000)

        libpangocairo-1.0.so.0 => /usr/lib/x86_64-linux-gnu/libpangocairo-1.0.so.0 (0x00007fa1da79d000)

        libcairo.so.2 => /usr/lib/x86_64-linux-gnu/libcairo.so.2 (0x00007fa1da488000)

        libpango-1.0.so.0 => /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0 (0x00007fa1da23c000)

        librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007fa1da034000)

        libXfixes.so.3 => /usr/lib/x86_64-linux-gnu/libXfixes.so.3 (0x00007fa1d9e2d000)

        libpangoft2-1.0.so.0 => /usr/lib/x86_64-linux-gnu/libpangoft2-1.0.so.0 (0x00007fa1d9c17000)

        libfontconfig.so.1 => /usr/lib/x86_64-linux-gnu/libfontconfig.so.1 (0x00007fa1d99d4000)

        libXrender.so.1 => /usr/lib/x86_64-linux-gnu/libXrender.so.1 (0x00007fa1d97c9000)

        libXi.so.6 => /usr/lib/x86_64-linux-gnu/libXi.so.6 (0x00007fa1d95b9000)

        libXrandr.so.2 => /usr/lib/x86_64-linux-gnu/libXrandr.so.2 (0x00007fa1d93ad000)

        libXcursor.so.1 => /usr/lib/x86_64-linux-gnu/libXcursor.so.1 (0x00007fa1d91a3000)

        libXcomposite.so.1 => /usr/lib/x86_64-linux-gnu/libXcomposite.so.1 (0x00007fa1d8fa0000)

        libXdamage.so.1 => /usr/lib/x86_64-linux-gnu/libXdamage.so.1 (0x00007fa1d8d9d000)

        libXext.so.6 => /usr/lib/x86_64-linux-gnu/libXext.so.6 (0x00007fa1d8b8a000)

        libselinux.so.1 => /lib/x86_64-linux-gnu/libselinux.so.1 (0x00007fa1d8968000)

        libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 (0x00007fa1d874d000)

        /lib64/ld-linux-x86-64.so.2 (0x0000562858ab0000)

        libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x00007fa1d84dc000)

        libffi.so.6 => /usr/lib/x86_64-linux-gnu/libffi.so.6 (0x00007fa1d82d4000)

        libxcb.so.1 => /usr/lib/x86_64-linux-gnu/libxcb.so.1 (0x00007fa1d80b1000)

        libicuuc.so.55 => /usr/lib/x86_64-linux-gnu/libicuuc.so.55 (0x00007fa1d7d1d000)

        liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x00007fa1d7afb000)

        libfreetype.so.6 => /usr/lib/x86_64-linux-gnu/libfreetype.so.6 (0x00007fa1d7850000)

        libxcb-shm.so.0 => /usr/lib/x86_64-linux-gnu/libxcb-shm.so.0 (0x00007fa1d764c000)

        libxcb-render.so.0 => /usr/lib/x86_64-linux-gnu/libxcb-render.so.0 (0x00007fa1d7441000)

        libthai.so.0 => /usr/lib/x86_64-linux-gnu/libthai.so.0 (0x00007fa1d7238000)

        libharfbuzz.so.0 => /usr/lib/x86_64-linux-gnu/libharfbuzz.so.0 (0x00007fa1d6fd9000)

        libexpat.so.1 => /lib/x86_64-linux-gnu/libexpat.so.1 (0x00007fa1d6db0000)

        libXau.so.6 => /usr/lib/x86_64-linux-gnu/libXau.so.6 (0x00007fa1d6bab000)

        libXdmcp.so.6 => /usr/lib/x86_64-linux-gnu/libXdmcp.so.6 (0x00007fa1d69a5000)

        libicudata.so.55 => /usr/lib/x86_64-linux-gnu/libicudata.so.55 (0x00007fa1d4eee000)

        libdatrie.so.1 => /usr/lib/x86_64-linux-gnu/libdatrie.so.1 (0x00007fa1d4ce5000)

        libgraphite2.so.3 => /usr/lib/x86_64-linux-gnu/libgraphite2.so.3 (0x00007fa1d4ac0000)

     

         3. Example: installed libglibmm with "sudo apt install libglibmm-*"

         4. Some packages were installed with newer/different versions so a soft link fixed that:

    This fixes libudev "sudo ln -s /lib/x86_64-linux-gnu/libudev.so.1.6.4 /lib/x86_64-linux-gnu/libudev.so.0"

    This fixes libssl "sudo ln -s /lib/x86_64-linux-gnu/libssl.so.1.0.0 /lib/x86_64-linux-gnu/libssl.so.1.0.2"

    This fixes libcrypto "sudo ln -s /lib/x86_64-linux-gnu/libcrypto.so.1.0.0 /lib/x86_64-linux-gnu/libcrypto.so.1.0.2"

     

         5. Once "ldd" was showing dependencies corrected I was able to launch and connect to my View Server

     

         6. I have one issue that I have not resolved, my Server info is not saved, so every connection I have to retype the Server name/IP to connect. Was able to save my most recent connection, so everything that I use on a regular basis is now working.


    0 0

    Doh! And it works probably on my Windows 7 VM because that was still set to USB 2 - probably because the VM is years old.

     

    Cheers, Rob.


    0 0

    А возможно ли такое в будущем:

    А вот как конкурент/замена разным Nas4free, "замёрзшим" FreeNas с OpenFiler, невнятным Nexenta`м и Open-E - почему нет?

    или тут другое?


older | 1 | .... | 5700 | 5701 | (Page 5702) | 5703 | 5704 | .... | 6576 | newer