0 votes
I ran into some error while using DSS through a virtual machine, I think it ran out of space, and now I can't start it anymore...

I'm getting this error: Dataiku Data Science Studio failed to start retrying...

I've tried reducing the size of the memory to 2 GB, it was ~10 GB before...

I've also tried renaming my databases folder to databases.old and restarting the virtual machine, but no luck...

Log:

00:00:02.669292 ******************** End of CPUID dump **********************
00:00:02.690537 PcBios: SATA LUN#0 LCHS=1024/255/63
00:00:02.690556 APIC: fPostedIntrsEnabled=false fVirtApicRegsEnabled=false fSupportsTscDeadline=false
00:00:02.690561 TMR3UtcNow: nsNow=1 533 413 424 021 623 300 nsPrev=0 -> cNsDelta=1 533 413 424 021 623 300 (offLag=0 offVirtualSync=0 offVirtualSyncGivenUp=0, NowAgain=1 533 413 424 021 623 300)
00:00:02.690570 VMEmt: Halt method global1 (5)
00:00:02.690577 VMEmt: HaltedGlobal1 config: cNsSpinBlockThresholdCfg=50000
00:00:02.690580 Changing the VM state from 'CREATING' to 'CREATED'
00:00:02.691090 Changing the VM state from 'CREATED' to 'POWERING_ON'
00:00:02.691108 AIOMgr: Endpoints without assigned bandwidth groups:
00:00:02.691110 AIOMgr:     D:\Dissertation_2018\dataiku-dss-4.3.1_1\dataiku-dss-4.3.1-disk001.vmdk
00:00:02.691388 Changing the VM state from 'POWERING_ON' to 'RUNNING'
00:00:02.691393 Console: Machine state changed to 'Running'
00:00:02.697583 VMMDev: Guest Log: BIOS: VirtualBox 5.2.16
00:00:02.697706 PCI: setting up resources and interrupts
00:00:02.698063 PIT: mode=2 count=0x10000 (65536) - 18.20 Hz (ch=0)
00:00:02.704859 ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={76eed314-3c72-4bbb-95cf-5eb4947a4041} aComponent={DisplayWrap} aText={Could not take a screenshot (VERR_NOT_SUPPORTED)}, preserve=false aResultDetail=0
00:00:02.710504 VMMDev: Guest Log: CPUID EDX: 0x078bfbff
00:00:02.718091 Display::handleDisplayResize: uScreenId=0 pvVRAM=0000000000000000 w=720 h=400 bpp=0 cbLine=0x0 flags=0x0
00:00:02.718219 GUI: UIFrameBufferPrivate::NotifyChange: Screen=0, Origin=0x0, Size=720x400, Sending to async-handler
00:00:02.719033 AHCI#0: Reset the HBA
00:00:02.719042 VD#0: Cancelling all active requests
00:00:02.719080 AHCI#0: Port 0 reset
00:00:02.719113 VD#0: Cancelling all active requests
00:00:02.719590 VMMDev: Guest Log: BIOS: AHCI 0-P#0: PCHS=16383/16/63 LCHS=1024/255/63 0x0000000003000000 sectors
00:00:02.719637 AHCI#0: Port 1 reset
00:00:02.863581 AHCI#0: Port 2 reset
00:00:03.028762 AHCI#0: Port 3 reset
00:00:03.193016 GUI: UIMachineViewNormal::resendSizeHint: Restoring guest size-hint for screen 0 to 800x600
00:00:03.193049 VMMDev: SetVideoModeHint: Got a video mode hint (800x600x0)@(0x0),(1;0) at 0
00:00:03.193086 GUI: UIMachineView::sltHandleNotifyChange: Screen=0, Size=720x400
00:00:03.193092 GUI: UIFrameBufferPrivate::handleNotifyChange: Size=720x400
00:00:03.193097 GUI: UIFrameBufferPrivate::performResize: Size=720x400, Directly using source bitmap content
00:00:03.194943 PIT: mode=2 count=0x48d3 (18643) - 64.00 Hz (ch=0)
00:00:03.210735 Display::handleDisplayResize: uScreenId=0 pvVRAM=000000000a870000 w=640 h=480 bpp=32 cbLine=0xA00 flags=0x0
00:00:03.210851 GUI: UIFrameBufferPrivate::NotifyChange: Screen=0, Origin=0x0, Size=640x480, Sending to async-handler
00:00:03.238230 GUI: 2D video acceleration is disabled
00:00:03.238286 GUI: HID LEDs sync is enabled
00:00:03.247948 GUI: UIMachineView::sltHandleNotifyChange: Screen=0, Size=640x480
00:00:03.248018 GUI: UIFrameBufferPrivate::handleNotifyChange: Size=640x480
00:00:03.248376 GUI: UIFrameBufferPrivate::performResize: Size=640x480, Directly using source bitmap content
00:00:03.261199 GUI: UIMachineLogicNormal::sltCheckForRequestedVisualStateType: Requested-state=0, Machine-state=5
00:00:05.669904 Display::handleDisplayResize: uScreenId=0 pvVRAM=0000000000000000 w=720 h=400 bpp=0 cbLine=0x0 flags=0x0
00:00:05.670087 GUI: UIFrameBufferPrivate::NotifyChange: Screen=0, Origin=0x0, Size=720x400, Sending to async-handler
00:00:05.670236 GUI: UIMachineView::sltHandleNotifyChange: Screen=0, Size=720x400
00:00:05.670270 GUI: UIFrameBufferPrivate::handleNotifyChange: Size=720x400
00:00:05.670319 GUI: UIFrameBufferPrivate::performResize: Size=720x400, Directly using source bitmap content
00:00:05.692006 PIT: mode=2 count=0x10000 (65536) - 18.20 Hz (ch=0)
00:00:05.692430 VMMDev: Guest Log: BIOS: Boot : bseqnr=1, bootseq=0002
00:00:05.694548 VMMDev: Guest Log: BIOS: Booting from Hard Disk...
00:00:11.515618 VMMDev: Guest Log: BIOS: KBD: unsupported int 16h function 03
00:00:11.515873 VMMDev: Guest Log: BIOS: AX=0305 BX=0000 CX=0000 DX=0000
00:00:11.525198 VMMDev: Guest Log: int13_harddisk_ext: function 41, unmapped device for ELDL=81
00:00:11.525488 VMMDev: Guest Log: int13_harddisk: function 02, unmapped device for ELDL=81
00:00:11.525792 VMMDev: Guest Log: int13_harddisk_ext: function 41, unmapped device for ELDL=82
00:00:11.526073 VMMDev: Guest Log: int13_harddisk: function 02, unmapped device for ELDL=82
00:00:11.526424 VMMDev: Guest Log: int13_harddisk_ext: function 41, unmapped device for ELDL=83
00:00:11.526704 VMMDev: Guest Log: int13_harddisk: function 02, unmapped device for ELDL=83
00:00:11.527004 VMMDev: Guest Log: int13_harddisk_ext: function 41, unmapped device for ELDL=84
00:00:11.527379 VMMDev: Guest Log: int13_harddisk: function 02, unmapped device for ELDL=84
00:00:11.527680 VMMDev: Guest Log: int13_harddisk_ext: function 41, unmapped device for ELDL=85
00:00:11.527961 VMMDev: Guest Log: int13_harddisk: function 02, unmapped device for ELDL=85
00:00:11.528425 VMMDev: Guest Log: int13_harddisk_ext: function 41, unmapped device for ELDL=86
00:00:11.528706 VMMDev: Guest Log: int13_harddisk: function 02, unmapped device for ELDL=86
00:00:11.529006 VMMDev: Guest Log: int13_harddisk_ext: function 41, unmapped device for ELDL=87
00:00:11.529349 VMMDev: Guest Log: int13_harddisk: function 02, unmapped device for ELDL=87
00:00:11.529649 VMMDev: Guest Log: int13_harddisk_ext: function 41, unmapped device for ELDL=88
00:00:11.529929 VMMDev: Guest Log: int13_harddisk: function 02, unmapped device for ELDL=88
00:00:11.530362 VMMDev: Guest Log: int13_harddisk_ext: function 41, unmapped device for ELDL=89
00:00:11.530680 VMMDev: Guest Log: int13_harddisk: function 02, unmapped device for ELDL=89
00:00:11.530980 VMMDev: Guest Log: int13_harddisk_ext: function 41, unmapped device for ELDL=8a
00:00:11.531456 VMMDev: Guest Log: int13_harddisk: function 02, unmapped device for ELDL=8a
00:00:11.531759 VMMDev: Guest Log: int13_harddisk_ext: function 41, unmapped device for ELDL=8b
00:00:11.532076 VMMDev: Guest Log: int13_harddisk: function 02, unmapped device for ELDL=8b
00:00:11.532445 VMMDev: Guest Log: int13_harddisk_ext: function 41, unmapped device for ELDL=8c
00:00:11.532802 VMMDev: Guest Log: int13_harddisk: function 02, unmapped device for ELDL=8c
00:00:11.533507 VMMDev: Guest Log: int13_harddisk_ext: function 41, unmapped device for ELDL=8d
00:00:11.533986 VMMDev: Guest Log: int13_harddisk: function 02, unmapped device for ELDL=8d
00:00:11.534551 VMMDev: Guest Log: int13_harddisk_ext: function 41, unmapped device for ELDL=8e
00:00:11.534860 VMMDev: Guest Log: int13_harddisk: function 02, unmapped device for ELDL=8e
00:00:11.535384 VMMDev: Guest Log: int13_harddisk_ext: function 41, unmapped device for ELDL=8f
00:00:11.535665 VMMDev: Guest Log: int13_harddisk: function 02, unmapped device for ELDL=8f
00:00:11.799874 GIM: KVM: VCPU  0: Enabled system-time struct. at 0x000000007ff79000 - u32TscScale=0xc587e750 i8TscShift=-1 uVersion=2 fFlags=0x1 uTsc=0x57f30e96b uVirtNanoTS=0x21ee60759
00:00:11.799920 TM: Switching TSC mode from 'Dynamic' to 'RealTscOffset'
00:00:11.855062 GIM: KVM: Enabled wall-clock struct. at 0x0000000046fa1888 - u32Sec=1533413433 u32Nano=186771849 uVersion=2
00:00:11.893287 PIT: mode=2 count=0x4a9 (1193) - 1000.15 Hz (ch=0)
00:00:11.990335 APIC0: Switched mode to x2APIC
00:00:12.089889 PIT: mode=0 count=0x10000 (65536) - 18.20 Hz (ch=0)
00:00:13.443050 AHCI#0: Reset the HBA
00:00:13.443072 VD#0: Cancelling all active requests
00:00:13.448374 AHCI#0: Port 0 reset
00:00:13.450125 VD#0: Cancelling all active requests
00:00:15.440630 NAT: Link up
00:00:27.486223 NAT: IPv6 not supported
00:00:27.718395 NAT: DHCP offered IP address 10.0.2.15
asked by
reshown by
Filesystem                                    Size            Used     Avail      Use %     Mounted on
/dev/mapper/centos-root     21G              20G              0       100%      /
devtmpfs                                      908M                0      908M            0%      /dev
tmpfs                                              920M               0       920M            0%     /dev/shm
tmpfs                                              920M        8.5M       911M            1%     /run
tmpfs                                              920M               0       920M             0%    /sys/fs/cgroup
/dev/sda1                                     976M       148M       761M           17%   /boot
tmpfs                                              184M               0        184M             0%   /run/user/1000
Thanks for the additional information. Indeed your virtual machine is full. Can you run "which psql" to confirm the location of the postgresql database? Can you launch a psql shell if you type "psql"?
When I type "which psql" I get: /bin/psql
When I type "psql" I get "could not connect to server: No such file or directory  Is the server running locally and accepting connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?
Anything else I can do?
??
Hi, the goal here is to clear as much space as possible in the virtual machine. The first steps would be to clear logs folder. Inside the Dataiku data directory https://www.dataiku.com/learn/guide/getting-started/dss-concepts/the-dss-datadir.html you can clear the jobs/ folder. Then can you re-run "df -h" and check what amount of space was cleared? If it is enough (a few GB) you can restart Dataiku (https://doc.dataiku.com/dss/latest/troubleshooting/problems/does-not-start.html).  Moving forward, to avoid that issue happening again, you will need to allocate more space to your virtual machine, or locate your data to external databases with more space.
Thanks, deleting worked, but I'm having trouble allocating more space to the virtual machine.  How do I locate my data to external databases with more space?  Note that the first link you provided doesn't work...
Hello, great to hear that deleting job logs worked. I fixed the first link. For allocating more space to your virtual machine, it depends on your admin rights and setup. Have you setup the virtual machine yourself? If so, using which virtualisation software? For locating data in external databases you can have a look at https://doc.dataiku.com/dss/latest/connecting/connections.html. Let me know if it helps.
I've installed the virtual machine based on following the instructions here:
https://www.dataiku.com/dss/trynow/virtualbox/

The disk image that I loaded is this one:
https://downloads.dataiku.com/public/studio/4.3.3/dataiku-dss-4.3.3.ova

However, this is set at 24 gigs, how can I expand its size?  I've tried a few different options, but Gparted doesn't seem to be able to read the partitions properly...
Thanks for the clarification. For expanding the size of your virtual machine, this is exclusively done on VirtualBox side. Dataiku then accesses the partition that you allocate in VirtualBox. There are some guides on the Internet covering this topic: https://www.ubergizmo.com/how-to/resize-virtualbox-disk/ for instance.
Thank you for the reply, and sorry for the delay in response since I've been travelling.
 Unfortunately, it seems the .vmdk file is not supported for resizing via VBoxManage (I get the error: "Progress state: VBOX_E_NOT_SUPPORTED", VBoxManage.exe: error: Resize medium operation for this format is not implemented yet!" .  I've tried copying the image to a larger drive using Ubuntu, but I'm not sure how to resize the partition using gparted since it appears to be lvm2 partition which gparted doesn't seem to be able to detect properly even after trying to install the lvm2 packages.  I'm not familiar with Linux, do you have suggestions on how to proceed?  

Alternatively, I guess I could install DSS from scratch on a new VM, but it's frustrating that the provided DSS disk image is limited to just 24 gbs.

Please log in or register to answer this question.

990 questions
1,023 answers
1,075 comments
2,828 users

©Dataiku 2012-2018 - Privacy Policy