Re: [gpc-informatics] #625: Disk space allocation and LVM setup for SNOW SHRINE spoke server(s)

[GPC Informatics]

#625: Disk space allocation and LVM setup for SNOW SHRINE spoke server(s)
--+
 Reporter:  kwanta|   Owner:  kwanta
 Type:  task  |  Status:  closed
 Priority:  critical  |   Milestone:  snow-shrine-2
Component:  data-sharing  |  Resolution:  fixed
 Keywords:|  Blocked By:
 Blocking:|
--+
Changes (by dconnolly):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 This is either done or not critical. Let's see if calling it done
 sticks...

--
Ticket URL: 

gpc-informatics 
Greater Plains Network - Informatics
___
Gpc-dev mailing list
Gpc-dev@listserv.kumc.edu
http://listserv.kumc.edu/mailman/listinfo/gpc-dev

Re: [gpc-informatics] #625: Disk space allocation and LVM setup for SNOW SHRINE spoke server(s)

[GPC Informatics]

#625: Disk space allocation and LVM setup for SNOW SHRINE spoke server(s)
--+
 Reporter:  kwanta|   Owner:  kwanta
 Type:  task  |  Status:  new
 Priority:  critical  |   Milestone:  snow-shrine-2
Component:  data-sharing  |  Resolution:
 Keywords:|  Blocked By:
 Blocking:|
--+

Comment (by hangs008):

 Replying to [comment:6 manuells]:
 > UTHSCSA:
 > We're short on hardware here and only have 8.5GB for the Snow Shrine
 server. UMN any way you guys can share your scripts for the compression
 and alerts? We will likely need something like that. Thanks!

 Our ops team uses zabbix and splunk to handle most things like this. If
 you need an easy way to compress your i2b2 logs you could set up a cron
 job to run
 {{{
 gzip /path/to/i2b2/logs/*.log.*
 }}}
 which would handle the logs that are automatically rotated out by
 jboss/wildfly. We disabled most of the console logging for jboss/wildfly
 so our console.log in /var/log/jboss-as doesn't get too large. If you
 needed to rotate that you could probably do something like
 {{{
 mv /var/log/jboss-as/console.log /var/log/jboss-as "console.log.$(date
 +%s)"
 touch /var/log/jboss-as/console.log
 gzip /var/log/jboss-as/console.log.*
 }}}
 gzip will automatically skip any files that are already gzipped so it
 saves some of the extra scripting work.

--
Ticket URL: 

gpc-informatics 
Greater Plains Network - Informatics
___
Gpc-dev mailing list
Gpc-dev@listserv.kumc.edu
http://listserv.kumc.edu/mailman/listinfo/gpc-dev

Re: [gpc-informatics] #625: Disk space allocation and LVM setup for SNOW SHRINE spoke server(s)

[GPC Informatics]

#625: Disk space allocation and LVM setup for SNOW SHRINE spoke server(s)
--+
 Reporter:  kwanta|   Owner:  kwanta
 Type:  task  |  Status:  new
 Priority:  critical  |   Milestone:  snow-shrine-2
Component:  data-sharing  |  Resolution:
 Keywords:|  Blocked By:
 Blocking:|
--+

Comment (by hangs008):

 UMN:
 We have 10G allocated to i2b2 and shrine including logging with 56%
 currently free. Our logs are on an automatic rotation that compresses the
 old files down to negligible sizes (2.2GB log down to 32MB archive). Our
 operations team also has automated alerts set up and will increase the
 filesystem if free space decreases too much.

--
Ticket URL: 

gpc-informatics 
Greater Plains Network - Informatics
___
Gpc-dev mailing list
Gpc-dev@listserv.kumc.edu
http://listserv.kumc.edu/mailman/listinfo/gpc-dev

Re: [gpc-informatics] #625: Disk space allocation and LVM setup for SNOW SHRINE spoke server(s)

[GPC Informatics]

#625: Disk space allocation and LVM setup for SNOW SHRINE spoke server(s)
--+
 Reporter:  kwanta|   Owner:  kwanta
 Type:  task  |  Status:  new
 Priority:  critical  |   Milestone:  snow-shrine-2
Component:  data-sharing  |  Resolution:
 Keywords:|  Blocked By:
 Blocking:|
--+

Comment (by lv):

 MCRI application server for i2b2:
 C: - 49.92 GB
 D: - 14.10 GB

 Eric thinks the SHRINE logs are on the D:, which means we'll probably need
 to increase resources.

--
Ticket URL: 

gpc-informatics 
Greater Plains Network - Informatics
___
Gpc-dev mailing list
Gpc-dev@listserv.kumc.edu
http://listserv.kumc.edu/mailman/listinfo/gpc-dev

Re: [gpc-informatics] #625: Disk space allocation and LVM setup for SNOW SHRINE spoke server(s)

[GPC Informatics]

#625: Disk space allocation and LVM setup for SNOW SHRINE spoke server(s)
--+
 Reporter:  kwanta|   Owner:  kwanta
 Type:  task  |  Status:  new
 Priority:  critical  |   Milestone:  snow-shrine-2
Component:  data-sharing  |  Resolution:
 Keywords:|  Blocked By:
 Blocking:|
--+
Description changed by kwanta:

Old description:

> To avoid having your spoke crash from log file growth, I'd like to get a
> response from the SNOW SHRINE spoke administrators from each GPC site
> with the amount of disk space allocated on your server.  If you have less
> than 30GB, you should talk to your system administrator to setup Logical
> Volume Management, or simply add more disk space to the existing logical
> group being used.
>
> If SHRINE is implemented on a Linux server, please run the following
> command on your SHRINE server(s) and your site abbreviation.
>
> df -BG
>
> MCRF and MU can simply respond with disk space allocated for the drive
> letters storing SHRINE and i2b2 application files.

New description:

 To avoid having your spoke crash from log file growth, I'd like to get a
 response from the SNOW SHRINE spoke administrators from each GPC site with
 the amount of disk space allocated on your server.  If you have less than
 30GB, you should talk to your system administrator to setup Logical Volume
 Management, or simply add more disk space to the existing logical group
 being used.  If your server crashes, it will also affect the other 10
 sites connected to the hub, so we'd like to avoid this if possible.

 If SHRINE is implemented on a Linux server, please run the following
 command on your SHRINE server(s) and your site abbreviation.

 df -BG

 MCRF and MU can simply respond with disk space allocated for the drive
 letters storing SHRINE and i2b2 application files.

--

--
Ticket URL: 

gpc-informatics 
Greater Plains Network - Informatics
___
Gpc-dev mailing list
Gpc-dev@listserv.kumc.edu
http://listserv.kumc.edu/mailman/listinfo/gpc-dev

Re: [gpc-informatics] #625: Disk space allocation and LVM setup for SNOW SHRINE spoke server(s)

[GPC Informatics]

#625: Disk space allocation and LVM setup for SNOW SHRINE spoke server(s)
--+
 Reporter:  kwanta|   Owner:  kwanta
 Type:  task  |  Status:  new
 Priority:  critical  |   Milestone:  snow-shrine-2
Component:  data-sharing  |  Resolution:
 Keywords:|  Blocked By:
 Blocking:|
--+

Comment (by kwanta):

 WISC PROD spoke:

 {{{
 Filesystem   1G-blocks  Used Available Use% Mounted on
 /dev/mapper/VolGroup-lv_root
66G4G   59G   6% /
 tmpfs   8G0G8G   0% /dev/shm
 /dev/sda1   1G1G1G  25% /boot]
 }}}

 WISC TEST spoke:

 {{{
 Filesystem   1G-blocks  Used Available Use% Mounted on
 /dev/mapper/VolGroup-lv_root
66G4G   59G   6% /
 tmpfs   8G0G8G   0% /dev/shm
 /dev/sda1   1G1G1G  20% /boot
 }}}

--
Ticket URL: 

gpc-informatics 
Greater Plains Network - Informatics
___
Gpc-dev mailing list
Gpc-dev@listserv.kumc.edu
http://listserv.kumc.edu/mailman/listinfo/gpc-dev

Re: [gpc-informatics] #625: Disk space allocation and LVM setup for SNOW SHRINE spoke server(s)

[GPC Informatics]

#625: Disk space allocation and LVM setup for SNOW SHRINE spoke server(s)
--+
 Reporter:  kwanta|   Owner:  kwanta
 Type:  task  |  Status:  new
 Priority:  critical  |   Milestone:  snow-shrine-2
Component:  data-sharing  |  Resolution:
 Keywords:|  Blocked By:
 Blocking:|
--+

Comment (by lpatel):

 At KUMC, we have allocated 60 GB.

 {{{
 $ df -BG
 Filesystem   1G-blocks  Used Available Use% Mounted on
 /dev/mapper/vg_core-root
59G   50G7G  89% /
 }}}

--
Ticket URL: 

gpc-informatics 
Greater Plains Network - Informatics
___
Gpc-dev mailing list
Gpc-dev@listserv.kumc.edu
http://listserv.kumc.edu/mailman/listinfo/gpc-dev