Static reports can be created through a command line interface, and on-demand reporting is supported through a Web browser CGI program. Data is visually presented within reports by tables and bar graphs. AWStats parses and analyzes server log files, producing HTML reports. Mkfs.AWStats ( Advanced Web Statistics) is an open source Web analytics reporting tool, suitable for analyzing data from Internet services such as web, streaming media, mail, and FTP servers. Warning: blocksize 8192 not usable on most systems. Mkfs.ext4: Size of device /dev/sdc1 too big to be expressed in 32 bits Next you'll expect to run mkfs, right? However: Warning: The resulting partition is not properly aligned for best performance. Or, you can make parted do that for you by using "0%" and "100%", and then running align-check: You can laboriously calculate by hand how big 34 sectors will be for your size disk, call it X, and set the start to X and the end to -X. However, with more massive disks, this is apparently insufficient due to the size of the metadata needed on the disk. ![]() With disks up to a certain size, the trick to avoiding the dreaded "Warning: the resulting partition is not properly aligned for best performance" is to use "1" for the start and "-1" for the end. Number Start End Size File system Name FlagsĪnd now make the first partition. Sector size (logical/physical): 512B/4096B If you are baffled about what the new device is called, check dmesg and/or just ls /dev and look for new, unused devices. where sdc is the new device that you haven't seen before. With CentOS 6, you have similar restrictions, but you don't have to prelabel the disks. (I will go into a few more details about how to use parted in the next section.) Note that the installer will refuse to use more than 2TB of the boot disk, no matter what. Any large data partions should be labelled "gpt". With CentOS 5, you want to use a utility like parted to manually create a boot partition and a system disk partition. I can tell you that this is much less of a pain with the CentOS 6 installer than with the CentOS 5 installer. I don't have great notes on this and can't go into much detail - apologies. Or, you may have a single 3TB hard drive, or a couple 3TB hard drives that you'd like to spread out across in your refurbished desktop tower. ![]() If you're going the USB key route, note that it has to be burned using the HP USB Key utility, which for some reason will not burn this particular utility from an image, but only from a CD (or image mounted as a CD). You will need to download and burn to CD or bootable USB key the HP Offline Array Configuration Utility (the "ACU"). ![]() Note that if you're dealing with HP products, the "ORCA", the raid utility that is available during boot, is not sophisticated enough to carve out a small RAID in this way. Then you can specify that linux will be installed on the small disk, and the installer won't choke. 10GB or whatever you judge is appropriate) RAID just for the system disk, and another for the data. If you've got a true RAID, you should be able to create a small (e.g. I hardly ever have to deal with truly large RAIDs or disks in a typical server - that's what NFS and Isilon and suchlike are for, amirite? So here's how you do it.ĭealing with a large boot disk/RAID during install If you try this fix, please watch your logs carefully. This does not appear to cause any issues, but please be wary of a crazy stranger's internet advice. I have a ticket open with Okta, but the short-term fix was to remove the serializer-2.7.2.jar from C:\Program Files\Atlassian\JIRA\atlassian-jira\WEB-INF\lib, and replace the xalan-2.7.2.jar there with xalan-2.7.0.jar (taken from the backup of the previous Jira version's install directory). : .Encodings.isRecognizedEncoding(Ljava/lang/String )Z ![]() 16:39:45,789 localhost-startStop-1 ERROR Unable to start JIRA due to Java Error. BeanCreationException: Error creating bean with name 'authenticationController' defined in URL : Instantiation of bean failed nested exception is : Could not instantiate bean class : Constructor threw exception nested exception is After re-enabling, it was throwing errors like: Jira startup was fine before re-enabling Okta. Just upgraded to Jira 6.4.7 (Windows, sigh), using Okta authenticator 1.0.9 (the most recent).
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |